27 replies to this topic

[Wonko the Sane]

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?

 

https://github.com/a...doc/memdisk.txt

d) MEMDISK normally uses the BIOS "INT 15h mover" API to access high

   memory. This is well-behaved with extended memory managers which load

   later. Unfortunately it appears that the "DOS boot disk" from

   WinME/XP *deliberately* crash the system when this API is invoked.

   The following command-line options tells MEMDISK to enter protected

   mode directly, whenever possible:

 

   raw Use raw access to protected mode memory.

 

   bigraw Use raw access to protected mode memory, and leave the

CPU in "big real" mode afterwards.

 

   int Use plain INT 15h access to protected memory. This assumes

    that anything which hooks INT 15h knows what it is doing.

 

   safeint Use INT 15h access to protected memory, but invoke

INT 15h the way it was *before* MEMDISK was loaded.

This is the default since version 3.73.

 

Wonko

 

[gnikolic]

Hello Wonko!

 

Thanx for replaying.

 

I had a problem with starting whatever ISO (Linux, DOS, Win) and not booting. It starts to boot via TFTP or HTTP just fine, but when it try to start itself, WinPE or Acronis DiskDirector in Linux just restarts computer and Windows from Hirens (Unlegal; it is well know) stops from starting with that EXCEPTION error message.

 

After putting that RAW sub-command with memdisk, booting and starting any ISO file is just Ok. 

HTTP is some 2x (or more) faster than TFTP and It is solved.

 

BR.

[reboot12]

I confirm - I also helped RAW parameter to load the ISO over HTTP - exactly HBCD14 MiniXP

 

:mxp14
echo Mini WinXP HBCD 14
initrd ${url}/mxp14.iso
chain memdisk iso raw || goto failed
goto start

Edited by reboot12, 01 May 2013 - 10:05 AM.