Dont know what is raw related to memdisk, but didnt know either that it is memdisk problem.
If somebody have info about memdisk and raw, please explain for me and others...
What is the difficult part?
d) MEMDISK normally uses the BIOS "INT 15h mover" API to access highmemory. This is well-behaved with extended memory managers which loadlater. Unfortunately it appears that the "DOS boot disk" fromWinME/XP *deliberately* crash the system when this API is invoked.The following command-line options tells MEMDISK to enter protectedmode directly, whenever possible:raw Use raw access to protected mode memory.bigraw Use raw access to protected mode memory, and leave theCPU in "big real" mode afterwards.int Use plain INT 15h access to protected memory. This assumesthat anything which hooks INT 15h knows what it is doing.safeint Use INT 15h access to protected memory, but invokeINT 15h the way it was *before* MEMDISK was loaded.This is the default since version 3.73.