Jump to content
Posted 23 December 2007 - 10:11 AM
Posted 23 December 2007 - 10:45 AM
Posted 23 December 2007 - 11:08 AM
<<...that i took out to put in a nother comp.>>
IDE-0 denotes the boot/system drive.
What version of XP (if using as boot drive), since XP OEM cannot be moved to another system as a boot/system drive?
Did you remove the drivers which do not apply to the new system and install the appropriate drivers for the second computer?
Did you check to see if the BIOS properly detected the drive? Auto detection does not always happen.
Did you ensure that the jumpers on all drives in the 2d system would be the same as the jumper on the drive you added?
Generally, you can use C/S or Master/Slave on the same cable, but you cannot combine drives which have dissimilar settings.
Is this change permanent or temporary?
Posted 23 December 2007 - 11:44 AM
Family and loved ones will always be a priority in my daily life. You never know when one will leave you.
Posted 23 December 2007 - 12:22 PM
When you take a hdd with a OS that you have been using on one computer and then install it as a master in another computer you are asking for major problems. The excerpt below is from an article from Intel which describes in detail what happens. The article also mentions a reference to an article by Microsoft, it can be seen here.
"Moving a hard drive with Windows* 2000 or Windows XP* already installed to a new motherboard without reinstalling the operating system is not recommended.
If a hard drive is moved to a new computer, the registry entries and drivers for the mass storage controller hardware on the new motherboard are not installed in Windows for the new computer and you may not be able to start Windows. This is documented in Microsoft's* knowledge base article †. This is true even if you move the hard drive to a motherboard with the same chipset, as different hardware revisions can cause this issue as well.
Additionally, moving a hard drive to a new motherboard may not exhibit any errors until you install new IDE drivers. This is because each chipset uses a different Plug-n-Play (PNP) ID to identify it. If you move your motherboard, your registry will have multiple PNP IDs (for the old hardware as well as the new hardware). If there are multiple entries in the registry, Windows cannot determine which hardware to initialize and therefore fails with a STOP error."
You can try running a repair with the installation, but I suspect that you will be reinstalling the OS.
Ho ho ho...merry xmas.
0 members, 0 guests, 0 anonymous users