XP Problem

[Crazy Horse]

I just replaced the C drive on the pc and went from windows 2000 pro to xp pro. Everything went good. Kept the 2nd drive F as a slave. Everything was and is now formatted w/ NTFS file sys.



The problem is "My Computer" does not show the 2nd hd set up as a slave. The replacement C drive is there. . . Both hard drive check out fine at Seagate's on line tools. They are both seen in Bios, device manager, and in XP's computer management visible and check out fine.



Thank you for any insight you may have.

 

[nickleinonen]

sata or pata cable connections on the hard drive? did you change the jumpers on the HD if so equipped?

 

[Crazy Horse]

I have tried master/slave configuration. That was the way they were configured prior. I also tried cable select and it's the same .

 

[DRAG DIESEL]

I have tried master/slave configuration. That was the way they were configured prior. I also tried cable select and it's the same .

I can walk you through this, but i am not going to type it all out. Feel free to call me at 916-425-1953. If you computer savy, poke arround in "disk manager", it's under administrative tools. You'll figure it out, if not, call.



~jake

 

[Todd G]

Do you have a Dell? I had the same problem and had to switch the SATA configuration to combined or something like that to get the second hard drive to show...

 

[DRAG DIESEL]

K, I am at my office computer that has XP.



Start Menu>Administrative Tools>Computer management



Under the storage tab, there is a sub catagory named disk management. If you see your drive under that, all is well. If not, you have to change your jumper... all hd's are different in the fact some will work on cable select, some have to be on slave, heck even some have be on master, when they are going to be a slave. So play arround with that.



If you disk is in that view all you have to do is give it a drive letter and make it an active disk in the system, and then your on your way. Like I said before, call if you have issues... i will try to walk you through it.

 

[Crazy Horse]

Jake, thanks for the phone help.



Todd, I do have a Dell 8100 or whats left of it that is. The original op sys (ME), harddrive and memory is a thing of the past. Where is this SATA? It seems to me when I first put the 2nd hd in a couple of years ago there was something I had do with switching to get the 2nd drive to show. That was when I was able to assign a letter to the drive.

 

[Todd G]

The setting was in the BIOS.

 

[RClark]

No problems like this with a MAC!

 

[Crazy Horse]

Well I posted a question to Western Digital, we'll see what they say.

 

[fest3er]

Jake, thanks for the phone help.



Todd, I do have a Dell 8100 or whats left of it that is. The original op sys (ME), harddrive and memory is a thing of the past. Where is this SATA? It seems to me when I first put the 2nd hd in a couple of years ago there was something I had do with switching to get the 2nd drive to show. That was when I was able to assign a letter to the drive.

I think ME is definitely pre-SATA (Serial ATA); IDE is almost certain. The only reasons I can think that XP wouldn't see a drive are:

- the second drive is deactivated in the BIOS

- the two drives are both configured as master or as slave on the same cable.

- you have another device installed (such as an ATA ZIP drive) that doesn't

obey IDE requirements and is interfering.



I would suggest you triple-check the drive jumper settings of all the drives in your system.



But since you seem to have done this already, there're few remaining possibilities: XP doesn't recognize the filesystem and/or partition type on the 'old' drive, or the cable is toast.

 

[Crazy Horse]

I think ME is definitely pre-SATA (Serial ATA); IDE is almost certain. The only reasons I can think that XP wouldn't see a drive are:

- the second drive is deactivated in the BIOS

I have been in bios both drives are there how would it be deactivated?



And would the second drive still be detectable in device manager, and in XP's computer/disc management and test out fine?



The ME was 2 op systems ago. 2000 pro has been on the pc for the last 4-5 yrs with the ntfs file sys. The only reason I replaced the C hd this time was because the op sys (2000) was on the C hd and I got the blue screen of death. The sys wouldn't boot up, -as soon as the desktop would begin to come up it would roll into another shut down and reboot. This was nonstop. The blue screen would come and go so fast you couldn't even read what the error was.



So this time around I thought I'd try XP Pro due to being a little more up to date than the 2000 pro. The original configuration w/ 2k pro was master/slave and they worked fine together. I thought there was something I had to do years ago when I put that 2nd drive in at the time. Flip some kind of a switch or something to get a drive letter (F) assigned to it and recognized.

 

[RandyHamilton]

The only reason I replaced the C hd this time was because the op sys (2000) was on the C hd and I got the blue screen of death. The sys wouldn't boot up, -as soon as the desktop would begin to come up it would roll into another shut down and reboot. This was nonstop. The blue screen would come and go so fast you couldn't even read what the error was.

The reason your pc was rebooting so fast was due to a default setting in both XP and 2k. I learned about it the hard way. You can change this default setting this way.



Right click my computer,

properties

advanced tab

startup and recovery button

remove checkbox from Automatically restart

ok your way out

 

[Crazy Horse]

The reason your pc was rebooting so fast was due to a default setting in both XP and 2k. I learned about it the hard way. You can change this default setting this way.



Right click my computer,

properties

advanced tab

startup and recovery button

remove checkbox from Automatically restart

ok your way out

Randy thanks for the advice I just unchecked the box on the new op sys. I'm wondering now if the old hd is still good??? May have to put it back in to road test.



I still can't see the 2nd hd on this xp's My Computer.

 

[Byershome]

If it was me, I disconnect the extra drive, reinstall and once I know everything is working correctly put the other drive in. Windows may have installed the boot loader on the "wrong" drive.

 

[Steve St.Laurent]

Did you have any system recovery software on that system? There was a package that was installed by default by Dell some time ago that caused this exact problem. I can't recall the name of the software unforetunately. To recover from it you had to boot the original drive up with that software installed, uninstall that software and then put the drive back online with your new drive. I had this happen to a client of mine and it took me a while to figure out the problem. What happens is that package changes the partition table such that base windows can't recognize it. If I saw the name of the program I'd remember it.

 

[Crazy Horse]

Did you have any system recovery software on that system? There was a package that was installed by default by Dell some time ago that caused this exact problem. I can't recall the name of the software unforetunately. To recover from it you had to boot the original drive up with that software installed, uninstall that software and then put the drive back online with your new drive. I had this happen to a client of mine and it took me a while to figure out the problem. What happens is that package changes the partition table such that base windows can't recognize it. If I saw the name of the program I'd remember it.

I had Norton "Go Back" on the old 2k op system I haven't put it back on this new C drive yet.



Are you saying that a data recovery software on the old system may have somthing to do with the old maintained F drive not being recognized on my new C drive w/XP Pro?

 

[Steve St.Laurent]

Yep - that's the app and that's your problem. Give me a few minutes and I'll find the fix for you.

 

[Steve St.Laurent]

Here you go: http://www.bleepingcomputer.com/forums/topic74951.html

What happens is Goback changes the partition type to a type 44 which XP doesn't recognize as an ntfs partition and therefore it is inaccessible. That fix above will convert it back to a standard ntfs partition and you'll be able to get everything off of it. It took me about 8 hours to figure this out for that client about 6 years ago.

 

[Crazy Horse]

Steve, thanks for the info! I'm off Weds and Thurs and I'll let you know how it comes out.