Hi cd-slic-ldr is grldr and has these builtin menu commands. you can try that. You can see the acpi command which you mst change to loadslic /oem.bin default 0 timeout 0 title Windows Vista acpi fallback 1 find --set-root /bootmgr chainloader /bootmgr title Windows NT/2000/XP fallback 2 find --set-root /ntldr chainloader /ntldr title Enter Command Line pause Boot failed! Press any key to enter command line. commandline
I've set up a 4 partition VM with 0 as containing boot info like hte recovery partition, 1 system reserved, 2 os and 3 data. I forced partition 0 to be type 0x12 and tested. no luck unfortunatley. The slic ldr that works is based on code 3 years older than now so maybe somethings changed. And the slicldr that works for you also works for me. but not my loader Any way it's worth a try.
Here's an update on how this loader is installed/executed which means it's quite difficult to take action against it. grldr is installed into the system reserved partition along with menu.lst and the slic file. no other alterations are made. Other loaders rename bootmgr and rename grldr as bootmgr so they get executed at boot time as the mbr default is to execute bootmgr. This is easy to detect, it's not the M$ bootmgr being executed. With this loader the MBR is amended to execute grldr which in turn executes the untouched bootmgr. Now compare this with an installation whereby the user installed Linux first, now uses grub4dos and then a valid puchased copy of Windows. The end result should (assuming Windows doesn't just walk all over the previous installtion) be the same. The only remaing difference is that the RSDP and SLIC are in the EBDA but as this is a valid place for them to be how can M$ tell if it's right or wrong that they are there. I hope this info is useful.
@nikmb Strange thing, EVEREST shows my 'real' modded SLIC 2.1 but SLIC DUMP Toolkit shows the SLIC loaded with the grldrslic iso, how come?
@Daz, you might look into the --ignore-oem directive added by nikmb, could be usefull for your LiveLoader CD
I'm not sure if it works already, I don't think it would try to boot any other partition as it specifically looks for bootmgr. I can't say for myself as I personally build all my systems and don't have an OEM drive to play around with. With the GRUB version I use here it has allot of stuff stripped from it and allot modified, I think we even use a different version to the one in use here. What nikmb has got done hes done well but theres still allot to do if he plans on supporting more systems and making the tables behave better.
And why is that? You hardly have done anything on that version... as far as i know it is made by zsmin Instead of acting superior, share the knowledge, help the community to improve it