Hi, lots of discussion going on, but the real question is: WHY can you load FDXMS with DEVLOAD and WHY does the same fail for FDXXMS and HIMEM? One guess would be: FDXXMS and HIMEM initialize the A20 state to off or leave the A20 off after init, and later XMS usage fails because A20 is off (guessing, would have to do in-depth source reading...)? When you load an XMS driver from config sys (rather than with DEVLOAD), then the KERNEL will detect the driver showing up and will (if DOS=HIGH) move most of the kernel and the BUFFERS to HMA. IF you use DEVLOAD, this would not happen, so the HMA will be unused. The kernel will also not go into "control A20 at program start" mode either. So DEVLOAD HIMEM would require sane default A20 state, and would not give you HMA usage. Still it would give you XMS usage, which makes the general "DEVLOAD HIMEM" useful. Would be interesting to know WHY it does not work out.
On the other hand, DEVLOADing is an exception. So if only FDXMS works with DEVLOAD, well, okay. Enough for the exception of having to use DEVLOAD at all. Still, I see no principal reason why DEVLOAD HIMEM should be ruled out. Eric ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
