moving SATA drive onto new mobo

[toecheese]

My old mobo blew so I bought a new ECS board. I moved my Windows XP
SATA boot drive over to the new mobo.

On the old mobo I had to set the SATA drive to IDE mode in the BIOS to
get it to work. The new mobo has no such BIOS setting. Now when I boot
the machine, it gets to the XP logo screen and then I get the BSOD. I
can't find anything in the BIOS to get the drive to work.

Is this a case of Windows needing the SATA drivers? If so is there a
way to add these drivers to my existing XP installation without having
to reinstall Windows and all my programs?

 

[Paul]

My old mobo blew so I bought a new ECS board. I moved my Windows XP
SATA boot drive over to the new mobo.

On the old mobo I had to set the SATA drive to IDE mode in the BIOS to
get it to work. The new mobo has no such BIOS setting. Now when I boot
the machine, it gets to the XP logo screen and then I get the BSOD. I
can't find anything in the BIOS to get the drive to work.

Is this a case of Windows needing the SATA drivers? If so is there a
way to add these drivers to my existing XP installation without having
to reinstall Windows and all my programs?

You could try a Repair Install. That preserves your data and installed
applications, but takes the OS back to the Service Pack level of the
install CD. Once done, you put back any remaining Service Packs,
go to Windows Update, and get the Security Updates again. If you had
an Internet Explorer later than the one on the install CD, you'd have to
reinstall that as well.

Repair install - stay out of Recovery Console...
http://www.michaelstevenstech.com/XPrepairinstall.htm

During the Repair Install, there'd be an opportunity to press F6 and
install any drivers needed. Since you didn't say what the new board
is (ECS model XXXX), it is pretty hard to guess just what kind of
drivers it might need. The motherboard CD may have a "Make Disk" utility
of some sort, for making a floppy with storage drivers on it. For
at least some chipsets (like Intel), it may be possible to install
using the default Microsoft storage driver.

When changing motherboards, I make an exact "clone" of the boot
disk, so if I screw up the process, I can start over again.

You can use Autostreamer, to make a new install CD from your
existing Windows CD. If your WinXP CD didn't have SP2 on it,
you could use Autostreamer to add it, then burn a new CD.
I did that for my Win2K CD, adding SP4 and making a new
Win2K SP4 install CD.

Paul

 

[toecheese]

During the Repair Install, there'd be an opportunity to press F6 and
install any drivers needed. Since you didn't say what the new board
is (ECS model XXXX), it is pretty hard to guess just what kind of
drivers it might need. The motherboard CD may have a "Make Disk" utility
of some sort, for making a floppy with storage drivers on it. For
at least some chipsets (like Intel), it may be possible to install
using the default Microsoft storage driver.

It's an ECS GF7100PVT-M3. I'm trying the Windows XP repair install now,
thanks.

Since the old mobo burned out, I couldn't clone the drive before moving
to the new mobo, and I don't have any other SATA machines. I'm pretty
much stuck with moving it as-is.

 

[Paul]

It's an ECS GF7100PVT-M3. I'm trying the Windows XP repair install now,
thanks.

Since the old mobo burned out, I couldn't clone the drive before moving
to the new mobo, and I don't have any other SATA machines. I'm pretty
much stuck with moving it as-is.

I went to the Nvidia site. There is a document on there
called "ForceWare_MediaShield_RAID_Floppy_install.pdf"

http://www.nvidia.com/object/nforce_630i_610i_winxp_16.08.html

ForceWare_MediaShield_RAID_Floppy_install.pdf
http://www.nvidia.com/attach/543918?type=support&primitive=0

"sataraid
--------
This folder contains the WHQL signed SATA RAID driver. If RAID is enabled in the
BIOS (even if installing to a non-RAID disk), you will generally use this. You can
determine if 'sataraid' is the correct folder to use for the F6 floppy by entering
the RAID setup screen in the BIOS. If you only see SATA devices listed, then this is
the correct folder.

legacy (called 'pataraid' in some packages)
-------------------------------------
This folder contains a non-signed driver for use with legacy BIOS that include PATA
RAID support. You can easily determine if the BIOS is a legacy BIOS by entering BIOS
RAID setup screen and observing if PATA devices are listed. If not, then 'sataraid'
folder should be used.

sata_ide
--------
This folder is NOT used for installation. This folder contains a non-RAID driver.
When installing with RAID disabled in the BIOS, the Windows storage driver is used.
Once OS install is complete then this driver can be installed using package setup."

Based on that, it sounds like the Windows storage driver can be used, if
RAID is disabled. In which case, no F6 and no driver floppy needed.

Paul

 

[PeterC]

WHENEVER you change the motherboard that is used by a harddrive containing
Windows, then you MUST reformat the harddrive and do a fresh install of
Windows. Otherwise you can look forward to ongoing Registry errors, BSOD's,
and data corruption. The old installation of Windows will not correctly use
the new motherboard.

Last time I changed the mobo I had 2 (cloned) HDs. Put 1 in, removed the
old drivers, installed the new ones and no problems since.
Once I was sure that everything was OK I recloned the disk. Been OK for 10
months now.

 

[toecheese]

WHENEVER you change the motherboard that is used by a harddrive containing
Windows, then you MUST reformat the harddrive and do a fresh install of
Windows. Otherwise you can look forward to ongoing Registry errors, BSOD's,
and data corruption. The old installation of Windows will not correctly use
the new motherboard.

I did a repair install of windows and so far, everything has been OK.

 

[geoff]

I agree with DaveW, moving a drive over as you describe is pushing the
envelope. An F-15 can only fly at 60K feet but if this were the 'alt.f-15'
newsgroup, I am sure some would post they flew it at 65K feet.

Pushing the envelope means variable results, IMHO.

--g

 

[Jim]

You have to buy a new license from Microsoft. Your license was for the
old mobo.

IME, I have never had a licensing issue/problem reinstalling WinXP on
a new harddrive or a new mobo.

 

[harikeo]

Nonsense. You will probably have to reactivate and may have to use the
phone, but I've done this a number of times with XP and haven't had to
buy a new license.

I thought Blattus had said wasn't true. I've never had to buy a new
licence from MS just because I've re-imaged a box or reinstalled onto
new hardware inc. mobo . Or is what Blattus said true for OEM copies
which are installed before delivery?

Vista is a different story.

How so? I have an image and with all the hardware changes I've made
since creating it I was surprised I wasn't asked to reactivate it.

 

[harikeo]

RobV wrote:

You have a real issue.