Any of you watching cvs commits will see I just commited some code to the dev branch to aid in win 3.x support when WIN31SUPPORT is defined. When this is not defined there is minimal changes to the kernel, however and this is my primary question it does restructure some variables marked 'FreeDOS specific entries' in the ListOfLists. Specifically I moved _os_setver_minor and _os_setver_major to be later (moving everything after them up) so I could use them for a structure passed to Windows. Does anything actually depend on these variables being at a specific offset? I assume not since they are marked FreeDOS specific and anyone wanting these should be accessed through other methods (or at least should have been noted as being used). I can revert this, but then I'll have to find somewhere else for some of data needed; currently I squeeze it into unused areas in the data segment so only the code size is increased.
Without tracing the code to figure out how it is used, can anyone tell me what _uppermem_root corresponds with? I need the last MCB in conventional memory (both to reference and to return an offset of a variable that stores it), is this available (_uppermem_root maybe?) or does it need to be added?
As noted in the commit message this is untested, use with caution! I will test once I find my copy of Win 3.x and install it... And yes there are still a bunch of FIXMEs in it. Basically all this does is handle Windows enter/leave/instancing requests. Comments are welcome.
Thanks, Jeremy
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Freedos-kernel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
