Install Vista on dual boot system

Ian Hodgson · 07-02-2007, 06:11 AM

Yes I installed XPHome to D: when XPPro was already on the C: Thats 3 years ago. Two weeks ago I replaced XPPro on C: with Vista and thats when I got the problems. Now that I recall I think the ACPI problem was already there cos something came up during the Vista install about ACPI compliance and I ignored it and it continued installing happily. Perhaps I shouldn't have ignored it.

PC eye · 07-03-2007, 03:57 AM

The answer to that is on the other thread you started in some sense. Vista has new hardware detection feaures and has a certain minimum requirement. You can run the MS download to see if your system is Vista compliant at any time. The Windows Upgrade Advisor 1.0 is available at http://www.microsoft.com/downloads/d...displaylang=en

Ian Hodgson · 07-05-2007, 02:55 AM

Thanks for your help. I have replaced Vista with XP for now. It was crashing when unattended for about 15 mins. Dont want to look into it right now. However when I re-installed XP on C: the boot loader wouldnt pick up my XP on D:. They are both on SATA drives. C: is on SATA 2 and D: is on SATA 1. I noticed that there are no files like ntldr or boot.ini on D: (not sure if they are supposed to be or not. I looked at the boot.ini file on C: (the new install) and it only had one line of disk info:
[boot loader]
;timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Home Edition" /noexecute=optin /fastdetect

It says rdisk 0 but this is SATA 2? not sure if that matters?

I tried adding another line

multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Micro soft Windows XP Home Edition on D" /noexecute=optin /fastdetect

but this made no change to the resulting boot

How do I get my D: to show up as a bootable drive?

Thanks

PC eye · 07-05-2007, 11:48 PM

For one thing the last part you added on the line is no good. The "on D" should be removed. You don't assign drive letters in the boot.ini file. As you must have noted by now the "rdisk(1)" refers to the physical drive installed. If you didn't load the needed sata drivers from a driver disk when going to install the new copy of XP on the second sata drive the installer didn't detect the copy of Windows on the other drive since it didn't even detect it. It created a totally new mbr on the current drive in use only.

07-03-2007, 03:57 AM	#12 (permalink)
PC eye Diamond Member Join Date: Apr 2006 Location: Inside a pc Posts: 20,474	The answer to that is on the other thread you started in some sense. Vista has new hardware detection feaures and has a certain minimum requirement. You can run the MS download to see if your system is Vista compliant at any time. The Windows Upgrade Advisor 1.0 is available at http://www.microsoft.com/downloads/d...displaylang=en __________________ What The Data Miners Are Digging Up About You http://abcnews.go.com/Technology/Tec...6355541&page=1 High Tech gifts for the Holidays under $150 http://abcnews.go.com/Technology/GadgetGuide/

07-05-2007, 02:55 AM	#13 (permalink)
Ian Hodgson New Member Join Date: Dec 2004 Posts: 15	Back to XP Thanks for your help. I have replaced Vista with XP for now. It was crashing when unattended for about 15 mins. Dont want to look into it right now. However when I re-installed XP on C: the boot loader wouldnt pick up my XP on D:. They are both on SATA drives. C: is on SATA 2 and D: is on SATA 1. I noticed that there are no files like ntldr or boot.ini on D: (not sure if they are supposed to be or not. I looked at the boot.ini file on C: (the new install) and it only had one line of disk info: [boot loader] ;timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Home Edition" /noexecute=optin /fastdetect It says rdisk 0 but this is SATA 2? not sure if that matters? I tried adding another line multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Micro soft Windows XP Home Edition on D" /noexecute=optin /fastdetect but this made no change to the resulting boot How do I get my D: to show up as a bootable drive? Thanks

07-05-2007, 11:48 PM	#14 (permalink)
PC eye Diamond Member Join Date: Apr 2006 Location: Inside a pc Posts: 20,474	For one thing the last part you added on the line is no good. The "on D" should be removed. You don't assign drive letters in the boot.ini file. As you must have noted by now the "rdisk(1)" refers to the physical drive installed. If you didn't load the needed sata drivers from a driver disk when going to install the new copy of XP on the second sata drive the installer didn't detect the copy of Windows on the other drive since it didn't even detect it. It created a totally new mbr on the current drive in use only. __________________ What The Data Miners Are Digging Up About You http://abcnews.go.com/Technology/Tec...6355541&page=1 High Tech gifts for the Holidays under $150 http://abcnews.go.com/Technology/GadgetGuide/

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Dual boot XP and Vista on the same HDD	staplerz	Operating Systems	1	03-09-2007 09:31 AM
Dual booting Xp and Vista	staplerz	Operating Systems	3	02-16-2007 05:11 AM
I cannot install Vista x64 on partioned drive	noho	Operating Systems	0	01-13-2007 12:44 AM
System boot failure, enter system disk on press enter???	Master Mind	Motherboards	10	08-25-2006 10:22 PM
Boot record not found on IDE-0 (dual-boot system)	mhodgins	Computer Memory and Hard Drives	4	10-10-2004 12:39 AM

07-02-2007, 06:11 AM	#11 (permalink)
Ian Hodgson New Member Join Date: Dec 2004 Posts: 15	Yes I installed XPHome to D: when XPPro was already on the C: Thats 3 years ago. Two weeks ago I replaced XPPro on C: with Vista and thats when I got the problems. Now that I recall I think the ACPI problem was already there cos something came up during the Vista install about ACPI compliance and I ignored it and it continued installing happily. Perhaps I shouldn't have ignored it.