Well, I finally got around to installing Vista Home Premium 64 bit. It did install without any problems on a new empty harddisk using the method described here (using two installs). I do have a slight problem with the dualboot setup though - it won't dualboot.
This may be because I installed Vista by changing the boot priority of the harddisks in BIOS. Normally I have the drive containing XP as the bootdisk, when installing Vista I moved the empty harddisk to the bootdisk "slot" to make it the "C" disk and moved the XP disk down in the boot priority.
So... The Vista bootloader was written to the (previously) empty harddisk and that harddisk now contains a partition with Vista on it. The old "C" drive (now "M") still has the XP installation and an XP bootloader. The Vista install did not modify the XP bootloader - I am able to restore the harddisk boot priority so that XP boots, I'm writing this from XP now.
I installed VistaBootPro (into Vista) and oddly on starting up it said that it could not find a copy of Vista, it's running in Vista for Pete's sake! Anyway I went ahead and added an entry for WinXP with the "M" drive designation (I had renamed the harddrives in Drive Management) and when booting I get a menu to select WinXP but when the XP entry is selected the computer just reboots - i.e. no Windows XP. This may be because I renamed the drives in Disk Management, I've forgotten what the "native" drive ID is for that partition - it might be "D", I haven't tried that yet.
Anyway, moving the bootdisk priority in BIOS does allow booting either Vista or XP, but it's not very convenient. So the question is whether the Vista dualboot bootloader needs to reference the harddisks by their plain vanilla "native" drive/partition IDs as you might see them in a DOS environment rather than by the IDs as seen inside the Windows OS (because you can rename them inside Windows)?
Or... Should I try installing VistaBootPro into XP and using the "install XP after Vista" solution for resolving the dualboot problem? The question is whether Vista will complain that its harddisk is no longer the bootdisk (drive "C" in the BIOS)?
This may be because I installed Vista by changing the boot priority of the harddisks in BIOS. Normally I have the drive containing XP as the bootdisk, when installing Vista I moved the empty harddisk to the bootdisk "slot" to make it the "C" disk and moved the XP disk down in the boot priority.
So... The Vista bootloader was written to the (previously) empty harddisk and that harddisk now contains a partition with Vista on it. The old "C" drive (now "M") still has the XP installation and an XP bootloader. The Vista install did not modify the XP bootloader - I am able to restore the harddisk boot priority so that XP boots, I'm writing this from XP now.
I installed VistaBootPro (into Vista) and oddly on starting up it said that it could not find a copy of Vista, it's running in Vista for Pete's sake! Anyway I went ahead and added an entry for WinXP with the "M" drive designation (I had renamed the harddrives in Drive Management) and when booting I get a menu to select WinXP but when the XP entry is selected the computer just reboots - i.e. no Windows XP. This may be because I renamed the drives in Disk Management, I've forgotten what the "native" drive ID is for that partition - it might be "D", I haven't tried that yet.
Anyway, moving the bootdisk priority in BIOS does allow booting either Vista or XP, but it's not very convenient. So the question is whether the Vista dualboot bootloader needs to reference the harddisks by their plain vanilla "native" drive/partition IDs as you might see them in a DOS environment rather than by the IDs as seen inside the Windows OS (because you can rename them inside Windows)?
Or... Should I try installing VistaBootPro into XP and using the "install XP after Vista" solution for resolving the dualboot problem? The question is whether Vista will complain that its harddisk is no longer the bootdisk (drive "C" in the BIOS)?
Last edited:
My Computer
System One
-
- Manufacturer/Model
- Gigabyte
- CPU
- e6600
- Motherboard
- Ga-965p-DS3
- Memory
- 4Gb
- Graphics card(s)
- BFG nv9800GTX-OC
- Sound Card
- X-Fi Fatal1ty
- Monitor(s) Displays
- Samsung 226CW
- Screen Resolution
- 1680x1050
- Hard Drives
- Maxtor 1Tb Maxtor 500Gb Maxtor 300Gb Maxtor 120Gb
- PSU
- Antec 650W
- Cooling
- Zalman 9700
- Mouse
- MX518
- Keyboard
- G15
- Internet Speed
- 330Kbps down