Ok, you are using RAMDISK booting, that of course works.
grub can also boot ISO without load to ram map ()/PE.ISO (0xff) (no --mem parameter).
but ISO need contig and i haven't success. anyway i like ramboot.
(bolding is mine)
The point, as per my post above, is that without RAMDISK booting it CANNOT work, until we find a "filedisk" type of driver capable of "taking" control once the "real" part of booting is over.
What I am trying to prevent is that a number of people, reading your report, may attempt (uselessly) to DIRECT booting a PE.ISO, which will fail.
Also, it is VERY important to have the "right" SETUPLDR.BIN, as said, and I am almost tired to post this all over:http://www.boot-land.net/forums/?showtopic=4952&st=2
Please note that:
Server 2003 files DO NOT work
Server 2003 SP1 files are KNOWN to work
Server 2003 SP2 files are reported to NOT work on a number of setups
Server 2003 R2 files are reported to work
No XP versions of the files have ever been reported to be working.
N.B.: "Traditionally" three files are needed:
SETUPLDR.BIN or SETUPLDR.EX_
Further tests have shown that ANY XP/2003 version of NTDETECT.COM work, and that SOME recent versions of RAMDISK.SYS do work.
Double check the SETUPLDR.BIN you have, it CANNOT be a Server 2003 one, the ability was introduced with Server 2003 SP1, if you do not trust me, you may want to trust either Bart Lagerwej:http://www.911cd.net/forums//index.php?showtopic=10806
or the actual people who wrote it:http://technet.microsoft.com/en-us/magazine/cc160905.aspx
Ramdisk booting, whilst VERY convenient with smallish .ISO's, has serious limits in both max size of the image (512 Mb using any of the MS ramdisk.sys drivers) and in required physical RAM on the machine.
More details are here:http://www.boot-land.net/forums/?showtopic=1507http://www.boot-land.net/forums/?showtopic=2692&st=26