NEW SATA DRIVE, OLD IDE Problem

[Stockmoose16]

Here's the story:
I bought a new SATA drive and need to transfer files to it from my old
IDE drive. The IDE drive doesn't have any OS on it, it was previously a
slave drive used to store files.

I hooked up the SATA drive, installed XP, everything worked fine. But,
when I hook in the IDE drive--as either a master or slave--the system
loads all the way up till I can see the desktop, and then immediately
crashes with a B.S.O.D.

Before the SATA drive was installed, the IDE drive in question was a
slave drive and worked fine (another IDE drive was the master).

What is causing this problem, and how can I fix it?

MSI PT880 Motherboard
Intel P4 3.2

 

[Ron Reaugh]

Here's the story:
I bought a new SATA drive and need to transfer files to it from my old
IDE drive. The IDE drive doesn't have any OS on it, it was previously a
slave drive used to store files.

I hooked up the SATA drive, installed XP, everything worked fine. But,
when I hook in the IDE drive--as either a master or slave

Determined how exactly? Describe cabling and jumpers. Is the IDE drive
recognized normally by the BIOS during POST before the OS comes into play?
Is the IDE FAT[32] or NTFS? What happens when you try a w98se boot floppy?

--the system

loads all the way up till I can see the desktop, and then immediately
crashes with a B.S.O.D.

What happens in Safe Mode?

 

[Jeff P]

Here's the story:
I bought a new SATA drive and need to transfer files to it from my old
IDE drive. The IDE drive doesn't have any OS on it, it was previously a
slave drive used to store files.

I hooked up the SATA drive, installed XP, everything worked fine. But,
when I hook in the IDE drive--as either a master or slave--the system
loads all the way up till I can see the desktop, and then immediately
crashes with a B.S.O.D.

Before the SATA drive was installed, the IDE drive in question was a
slave drive and worked fine (another IDE drive was the master).

What is causing this problem, and how can I fix it?

MSI PT880 Motherboard
Intel P4 3.2

Did your old drive have a primary or extended partition? Primary partitions
take precedence to secondary partitions for drive letter assignments. You
might be causing the drive letters to be rearranged when you boot up this
way, which would cause Windows to not be able to access any of its files
after it kicks past a certain stage in the boot process.

-Jeff

 

[Folkert Rienstra]

Did your old drive have a primary or extended partition?

What do *you* think if he previously booted from it?

Primary partitions
take precedence to secondary partitions for drive letter assignments.

Not with XP.

 

[Folkert Rienstra]

Here's the story:
I bought a new SATA drive and need to transfer files to it from my old
IDE drive. The IDE drive doesn't have any OS on it, it was previously a
slave drive used to store files.

I hooked up the SATA drive, installed XP, everything worked fine. But,
when I hook in the IDE drive--as either a master or slave--the system
loads all the way up till I can see the desktop, and then immediately
crashes with a B.S.O.D.

Before the SATA drive was installed, the IDE drive in question was a
slave drive and worked fine (another IDE drive was the master).

What is causing this problem, and how can I fix it?

There may be something wrong with the structures on the drive.
That may not have been a problem when XP was booting from it
but may be when it is discovered as a data drive by XP.
A crash for that is excessive though.

You can also try obscuring the previous installation of XP on that drive,
e.g. by renaming the directory it's in, in case XP has a problem with that.

 

[Rod Speed]

Here's the story:
I bought a new SATA drive and need to transfer files to it
from my old IDE drive. The IDE drive doesn't have any OS
on it, it was previously a slave drive used to store files.

I hooked up the SATA drive, installed XP, everything worked fine.
But, when I hook in the IDE drive--as either a master or slave--
the system loads all the way up till I can see the desktop,
and then immediately crashes with a B.S.O.D.

Sounds like its trying to boot off the IDE when its installed.

Most likely the bios has been told to boot off the IDE and does
so when its present. When its not, it looks for other bootable
drives and boots off the SATA when the IDE isnt present.

Before the SATA drive was installed, the IDE drive in question was
a slave drive and worked fine (another IDE drive was the master).

What is causing this problem, and how can I fix it?

See if you can tell the bios to boot off the SATA
drive. Likely the IDE drive is higher in the boot
sequence order. Move it below the SATA drive.

If you cant do that for some reason, you should be
able to wipe the IDE drive with something like clearhdd
if you dont care about its contents. Do that with just
the IDE plugged in with clearhdd on floppy etc.

 

[Rod Speed]

Did your old drive have a primary or extended partition? Primary partitions
take precedence to secondary partitions for drive letter assignments.

XP doesnt do it that way.

You might be causing the drive letters to be rearranged when you boot up this
way,

Maybe, but that shouldnt produce a BSOD.

which would cause Windows to not be able to access any of its files after it
kicks past a certain stage in the boot process.

Most likely its just booting off the IDE when its present.

 

[Jeff P]

XP doesnt do it that way.

You're correct. I guess I wasn't paying attention here. However, I have had
situations come up in which Windows XP would rearrange the drive letters on
me while adding and removing drives.

Maybe, but that shouldnt produce a BSOD.

I haven't had this cause a BSOD, but I did get windows to hault on the login
screen simply because I changed my secondary hard drive. That situation was
highly irritating.

Most likely its just booting off the IDE when its present.

Now that you mention it, I agree. This sounds like the most likely cause.
OP: Did you have a windows installation on this drive at some point,
possibly from another machine? It might not like booting with a completely
new array of hardware.

-Jeff

 

[Rod Speed]

You're correct. I guess I wasn't paying attention here. However, I have had
situations come up in which Windows XP would rearrange the drive letters on me
while adding and removing drives.

Sure, but it shouldnt with the specific addition
of the IDE drive to working system that he has.

I haven't had this cause a BSOD, but I did get windows to hault on the login
screen simply because I changed my secondary hard drive. That situation was
highly irritating.

Sure, but he is getting a BSOD, that shouldnt be seen even
if XP is stuffing up the drive lettering for some reason.

Now that you mention it, I agree. This sounds like the most likely cause. OP:
Did you have a windows installation on this drive at some point,

Yes, he said that it used to boot off that drive, before
the SATA was added and XP was moved over to that.

possibly from another machine? It might not like booting with a completely new
array of hardware.

That did work fine, from the SATA drive.

Most likely the bios is still set to boot off the IDE and when
it isnt connected, it boots off the SATA fine. When the IDE
is plugged in again, the bios finds it and boots off it and
its the old XP install on that that's now BSODing when it boots
off the old IDE drive now.

 

[Stephen]

Here's the story:
I bought a new SATA drive and need to transfer files to it from my old
IDE drive. The IDE drive doesn't have any OS on it, it was previously a
slave drive used to store files.

I hooked up the SATA drive, installed XP, everything worked fine. But,
when I hook in the IDE drive--as either a master or slave--the system
loads all the way up till I can see the desktop, and then immediately
crashes with a B.S.O.D.

Before the SATA drive was installed, the IDE drive in question was a
slave drive and worked fine (another IDE drive was the master).

What is causing this problem, and how can I fix it?

MSI PT880 Motherboard
Intel P4 3.2

Put it in an external usb enclosure to copy the files.

Stephen


--

 

[Folkert Rienstra]

Put it in an external usb enclosure to copy the files.

Very strange. Can you shed some light on whether it was your
old IDE that booted up instead of the SATA?
And if so, does your IDE still bootup when only by itself.