![]() ![]() Theoretically the Icecube one's is "better" as it provides an Exchange for the disks, whilst yours re-maps just the "found" disk to (hd0) (and the actual original first disk becomes "nowhereland"). Not really-really (in the sense that BOTH the one posted by Icecube and by you may fail on some particular configuration). Whoops, this post actualy should have been posted here: ![]() Hope this is usefull, and someone maybe can verify this. This one is able to konboot proper, no matter which (hdX) the UDF or Windows-device is, and even if Plop was loaded. But please let know if I'm wrong.įind -set-root -ignore-floppies -ignore-cd /bootfiles/konFLOPPY.imgįind -set-root -devices=h /ntldr & map () (hd0)įind -set-root -devices=h /bootmgr & map () (hd0) My method seems way more easy and functional to me. What if the Windows device you need to boot is not hd1? - The example above won't work. Well, it looks for the UDF-device-number, but. I just don't get the point of checkrange in konboot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |