I have a Dell 9200-DXP061 tower PC with 2 GB RAM upgraded BIOS of 2.5.3 with a newly formatted and partitioned WD500GB SATA HDD running WinXP Pro/SP3 and connected at SATA 0. This WD500GB SATA HDD was purchased and installed specifically because the previous WD160GB SATA HDD was only about 30% full, has/had the O/S WinXP Pro SP3 in addition to my usual complement of photos, etc but will not boot when used as the primary. I am able to slave this WD160 externally via USB connection. All the directories and files appear intact and easily accessible as F: drive.
I would like to return this WD160 SATA internally in the second HDD bay and use it as a backup file. When I attempt to install internally, despite configuring BIOS it is only seen as "Unknown" under SATA port 1 or SATA 4 (if I reconnect as an altenative to SATA 1). This WD160 is NOT seen in DMgr or Disk Mngment. Further, and even worse, when I boot up after attempting to connect the WD160 to SATA 1 port (not SATA 0 where my primary O/S and WD500 connects), I get a BSOD STOP 0x7B and the process freezes. This is exactly the screen I saw when this WD160 was previously used as the primary HDD in SATA 0 and the reason I bought the new WD500GB HDD and re-installed WinXP Pro sp3 as the primary boot HDD.
I have run a rootkit Anti-virus scan twice on both SATA HDD's using AVG Pro. I also ran an online antivirus scan with Kapersky and Norton on another PC also running WinXP Pro sp2 with no viruses found on the 2nd PC's 2 HDD or this WD160 slaved via USB connection on the 2nd PC.
In summary, I can't use the older WD160 SATA HDD as a slave/backup except externally connected via USB in a BlacX box. There are no jumpers to change with either WD160 or WD500 HDD and it is my understanding that the OS simply selects the SATA 0 as the primary/master and the SATA1-5 as slaves. In the BIOS the CD-ROM drive is set for SATA1, DVD-ROM/RW is the SATA 2. My floppy drive (yes, I still like them) runs via EIDE/PATA. I tried a combo SATA/Mobex connector for the WD160 connection to SATA 1 and SATA 4 but thinking it was too cheap of a connector and may not have been sending power/data properly, I scavenged the native SATA cable off the CD-ROM and used a separate extra power plug (not Mobex) available in the tower. I reset the BIOS boot sequence to floppy, WD500, WD160, CD-ROM, USB. Again got the BSOD STOP 0x7B. I've researched the STOP 0x7B codes and can't really determine what to do at this stage.
Short of transferring all the important files off the WD160, then repartitioning and reformatting the WD160 is there any way to "make" the WD160 "behave" as a slave internally?
Can I/should I remove the WinXP Pro O/S from the WD160 so there will not be any conflicts with boot up? How is that accomplished since Add/Remove programs is only available for the C: drive and my WD500GB SATA HDD? It doesn't sound right to simply delete the \Windows\system32 files in the F: drive (the WD160 HDD containing the old WinXP Pro sp3).
I appreciate any and all ideas and hope I've been clear about my issue.