I think I see where you've gone wrong. You have moved the original seagate C drive from Primary Master to Primary slave and then installed XP Pro onto the new primary master Qantum drive. Do this: Put the seagate drive back as primary master. Put the Qantum in Slave position. Format the Qantum. Put the XP Pro CD in and reboot. Reinstal XP Pro to the slave drive. Dualboot will then be properly configured. Give a man a fish and you feed him for a day. Teach him to fish and his wife will never forgive you.

0

thanks a lot mate i'll try that. This is a business PC so it needs to be up and running fast!

0

Just one more thing- do I have to reformat? I just installed all of my apps!

0

I suspect that when you installed Pro on the new "Primary Master" It set itself as a C drive so you in effect have two C drives. It isn't possible to change the drive letter of a System drive so I think it will need to be reformatted so that it is properly configured as D when you put it in the slave position. Give a man a fish and you feed him for a day. Teach him to fish and his wife will never forgive you.

0

This is an interesting little situation - and not all that difficult to resolve. My post may be a a little academic...; but it does help to explain the what/why/how of it all and may be useful to know for future use? If I’m reading this aright… Quantum is Master to Barracuda Slave; Barracuda has Home on installed, Quantum has Pro installed. Quantum was set as Master with Barracuda installed as Slave and then Pro installed to Quantum. Now you boot only to Quantum (Pro). Presuming so this is is why you have the situation that you have now. When Barracuda was “alone” (as Master and Home installed) Home was by default installed as c:\windows). Its boot.ini reflects Home installed in that configuration (multi-0… partition-1). If/when you installed Pro (on the Quantum) there was no evidence of a boot.ini on that Quantum drive that referred to Home on Barracuda drive (and if it was a blank drive then there wouldn’t be) then Pro setup would not ordinarily detect the Home installation on the Slaved drive… There are at least two ways to overcome that situation. (Also Home went in as c:\windows; I think Pro will have gone in as winnt?). For the Barracuda/Home to appear and boot via the boot-menu on the Quantum (set as Master) there must be a reference in the boot.ini on the Quantum (Master/Pro) drive to the Home installation on the Slaved Barracuda. That line/reference must also reflect the “new/changed” status of the Barracuda drive; i.e. multi-0 now becomes multi-1; the balance of the line remains the same. You could simply copy the main/single-line reference to Home in the boot.ini on the Barracuda drive to the boot.ini on the Quantum; then change the multi-o reference to multi-1 in that copied line as already detailed just above. This of course presumes you do have a boot.ini on the Quantum/Master; more on this missing item below. However, one item doesn’t make sense here. As you are able to boot to the Quantum and thus to Pro, I am puzzled as to why the Quantum is shown as d: … I would have expected it to be shown as c: (in Pro-Explorer) - presuming you did configure/format it during Pro setup (i.e. it was NOT preconfigured/prepartitioned – formatted or not)? I would however expect the Barracuda (when not booted) to be shown in Pro-Explorer (when booted) as something other than c: ; to still showing itself as c: when booted up (in Home-Explorer). Likewise the Quantum will be shown as something other than c: when viewed via Home-Explorer, and shown as c: when booted up. My experience has been that two such OS (each on its own drive) will “flip-flop” the drive labelling for the non-booted drive when viewed from the booted OS… Initially Home went in as c:\windows (Barracuda was only drive present). Even when this drive is now set to Slave posn. (and when it boots) it will still boot with its path showing c:\windows etc. Albeit at present it doesn’t boot as there is no boot-menu option to allow it – more on that anon. You say the new Master (the Quantum) shows as d: ??? If this drive was installed unconfigured (no partition/s) then this drive would (should) also show as c: when Pro went in… (even with the Barracuda connected as Slave). How do you manage to get the new Master to show up as d: ??? The missing boot-menu on the Quantum: I recall coming across this irritation a while back and have managed to recall at least one reference to how/why it occurs… viz http://www.winnetmag.com/Windows/Article/ArticleID/41671/41671.html It refers to W2K and later OS... The article details using a boootcfg routine to resolve the omission. The other way is to manually create a boot.ini (via Notepad/Wordpad. You can also use the bootcfg routine to detect and add the other XP (Home) installation to the newly created boot.ini on the Quantum (or simply copy over and modify the entry from the original Home boot.ini on the Barracuda) viz: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/bootcfg.mspx This second M$ KB is probably more the one you want in this regard. http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/bootcons_bootcfg.mspx And JSINC discusses it too at: http://www.jsiinc.com/SUBM/tip6100/rh6136.htm Both Pro and Home will boot as c: ... Hope the above helps resolve it all, and isn’t too lengthy and/or confusing… Richard (post-7) suggests resetting the Barracuda as Master to Quantum and re-installing Pro afresh. It would work but isn't necesary to go that far... You could reset drives with Baracuda as Master and Quantum (with Pro still installed there) and simply run the bootcfg routine to locate/detect/and add Pro to Home boot.ini... Again both OS will boot as c: . Personally I'd leave the drives as they are (Master = Quantum, Barracuda = Slave) and run the bootcfg routines as appropriate. 'Should do all that's needed.

0

Just 1 more thing- Can't I just switch the hard drives over? I just installed all my programs!

0

I don't want to do all of that bootconfig stuff- i'll just reformat the Quantum Hard Drive. But I just wasted an afternoon of reinstalling Windows and apps!!! But thanks again for all of your help, Matty

0

Don't understand your decison (perceived need) to reformat the Quantum as a solution to your problem??? What happens after that? Presumably the Quantum is still Master afterwards; or are you intending to reset the Barracuda as Master to Quantum as Slave and then (re-)install Pro to Quantum (which would work - but so much time/effort...)? The bootcfg routine/s ("all" that's needed...) would have been the easier route to get it working - drives installed configured etc. as is? There would be need to reformat the Quantum and thus go thru' a re-install etc... The bootfg routine is ideal for your situation (Quantum as Master, all items installed, and need to add the Barrucuda to the boot.ini list thereon)? As regards switching drives, it also would be a quicker and easier solution than a re-install etc. of the Quantum. All you would have to do is to add a line referring the the Quantum installation in the boot.ini on the Barracuda (then restored as Master to Quantum set as Slave). Or, again, run the appropriate bootcfg routine to detect/add the Quantum to the Barrucuda boot.ini... In any of the these routes both OS installations would boot as C: as that info is stored in the registry and is referred to during boot-up. That will cause you no problems.

0