Hi there,
I have been reading the HIMEM sources, and have these questions. I am grateful to whoever can say something about these questions (which as usual are plain questions with no critisizing):
(1) There is a /TEST option (not present in MS-HIMEM), and at the same time, MS-HIMEM implements a /TESTMEM:ON|OFF option to do this (defaults to ON). /TEST does a nice test by allocating, filling, testing, resizing,..... to determine the reliability of the extended memory.
I just wanted to ask if there's something I missing about something which is obvious (?)
(2) This is something about TASM/MASM: what is a COMMENT block?
(3) XMS UMB functions are not supported. I just wonder if MS-HIMEM implements them: now that HIMEM is quite machine specific, perhaps this is the way Microsoft implement their "UMBPCI" (just a reflection)
(4) Finally, I am unable to understand the whole process behind making a mixed SYS/EXE driver, can someone clarify about this?
- HIMEM64 starts with a device driver header
- HIMEM.EXE actually starts with "MZ", so it can be open as an executable. How is that the kernel can open it as a driver, if it doesn't start with the device driver header?
- Who calls ASMSTART_EXE?
Thanks in advance for your help, Aitor
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
