At 10:12 PM 2/10/2005 +0100, Bernd Blaauw wrote:
However, when loading HIMEM, Memtest+ (www.memtest.org) crashes, as it does not like any XMS manager.
I wish we had a commandline XMS enabler (HIMEM /ENABLEXMS for example) to mimic the behaviour of XMSMMGR.EXE on a Windows installation cdrom.
I don't have a clue how this would work, but it sounds a terrible idea. XMS manager is not the sort of thing you stick in after other device drivers have loaded. There's little to no way to make sure you don't stomp on already loaded drivers. The XMS/HMA driver needs a clean memory map to operate. Same goes for turning XMS off after it's been turned on. Where do the drivers already loaded in extended memory go?
The real problem is that there exists software which was not properly written to accommodate a low-level memory manager. Or, perhaps in the case of MEMTEST which appears to need bare metal access, the problem is that you can't expect it to ever co-exist with a memory manager in the same operating session.
Only way for me to check if XMS is enabled is: IF EXIST XMSXXXX0 echo XMS manager loaded..
What's wrong with that? Checking driver name is the right way to see if there is an loaded and active XMS driver. In fact, for EMS that's a documented EMS specification method to check for whether an EMS driver can be used by an application.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
