- How to use kon boot windows 8 install#
- How to use kon boot windows 8 upgrade#
- How to use kon boot windows 8 full#
- How to use kon boot windows 8 windows 8#
If you have Norton Ghost or Acronis True Image handy, cloning your drive/partition is probably the best way to recover from any problems you might run into. This is a simple procedure, but there's always a risk of data loss whenever you modify disk partitions.
How to use kon boot windows 8 install#
To configure your PC for dual-boot, all you have to do is create a new partition for Windows 8, then install it.Ĭaution: Before you begin, make sure to back up your system.
How to use kon boot windows 8 windows 8#
This will let you use both operating systems, side-by-side, until you're comfortable enough with Windows 8 to go all in.
How to use kon boot windows 8 upgrade#
And a map -reset could save the one or other reboot.If you have a Windows 7 PC but aren't sure you're ready to upgrade to Windows 8 yet, a dual-boot system might be a good way to ease into it. I would like also to see something like "find -skip=(hdx)" or -skip-usb-connected. yeh, this may simplify some mapping situations. (Yes not every, on some idiotic cfg it does not, at least not XP)Ībout your suggested feature. I emulated a range of configurations in VMware and tried different physical ones. Of course you're free to split it into single entries for XP and Vista as well. (Just edit'n delete the "find /bootmgr" line, to boot XP) This way I also got the possibility to choose between XP and Vista, in case of both are installed. Once the OS is booted, all drives are available. In what I've tried, the 2nd mapping-step seems not needed.
How to use kon boot windows 8 full#
Well, I think a full exchange of the drives can be done like.įind -set-root -devices=h /ntldr & map () (hd0) | map (hd0) ()įind -set-root -devices=h /bootmgr & map () (hd0) | map (hd0) () īTW IMHO what we still miss (unless I am mistaken and it has been added lately ) is a "SHIFT" and "circular stack", that might become handy in a number of situations, compare with this: The issue with Icecube's approach might be that you will anyway map first disk (first disk without the UFD connected) to (hd0).īOTH will work in all most common setups though let's say conventionally on 99.91% of setups. The issue with your approach is that since you are "looking" for a bootloader file that may be on different disks, the disk where bootmgr is will alway "prevail" on the one hosting ntldr, thus you might be unable to recover the NT/2K/XP/2003 install (but access the Vista /Server 2008/7 one). 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 kommentar(er)
