Can XP Pro be installed on a SATA drive?


D

Doc

I got a 320 gig SATA WD Caviar drive to install XP Pro on a Core2 Duo
machine. I get as far as the last stage or so of the install and got a
blue screen "A problem has been detected and Windows has been shut
down to prevent damage to your computer" If this is the first time
you've seen this yada yada yada - then Stop 0x00000024 (0x001902FA,
0xF76A6300, 0xF76A6000, 0x805380B2)

I saw a mention somewhere that XP doesn't support SATA. Not sure how
that can be if I've been running this machine with auxilliary SATA
drives installed on it. Why would it let me get this far in the
installation process? Of course I don't know for sure what the root
cause of the problem was to begin with. I decided to try a different
drive since I seened to have ongoing issues ever since installing that
other IDE drive and the drive was on sale under $50 for 320 gigs.

Thanks for all input
 
Ad

Advertisements

B

BillW50

I got a 320 gig SATA WD Caviar drive to install XP Pro on a Core2 Duo
machine. I get as far as the last stage or so of the install and got a
blue screen "A problem has been detected and Windows has been shut
down to prevent damage to your computer" If this is the first time
you've seen this yada yada yada - then Stop 0x00000024 (0x001902FA,
0xF76A6300, 0xF76A6000, 0x805380B2)

I saw a mention somewhere that XP doesn't support SATA. Not sure how
that can be if I've been running this machine with auxilliary SATA
drives installed on it. Why would it let me get this far in the
installation process? Of course I don't know for sure what the root
cause of the problem was to begin with. I decided to try a different
drive since I seened to have ongoing issues ever since installing that
other IDE drive and the drive was on sale under $50 for 320 gigs.

Thanks for all input
Yes, it is true. Windows XP doesn't come with any SATA drivers and you
must (if you need them) install them in the very beginning of the
install by pressing F6 to install RAID, SATA, or any other device
driver(s) to work with Windows XP. And this is usually done by having
the driver(s) on a floppy disk. Yes an USB floppy drive will work too.

If you are using a recovery disc to install XP and not a MS one, odds
are good that it includes the driver that you need. So you don't have to
worry about it. Another thing one can do without the driver on some BIOS
is toggle a setting for the drive. It will read and write a tad slower,
but you can get by without a driver.

Having said all of this, I don't believe this is your problem. As if it
was, the install couldn't see the SATA drive in the first place to start
the install.

Now that STOP 0x24 error is the key to your whole problem. Basically it
means your file system is corrupt. So now what? Well here is pretty good
advice and it is a good start. And good luck!

http://www.geekswhoknow.com/articles/stop-0x00000024-0x0000024-0x24-ntfs-file-sys-error-code.htm
 
K

Ken Blake, MVP

I saw a mention somewhere that XP doesn't support SATA. Not sure how
that can be if I've been running this machine with auxilliary SATA
drives installed on it.

It's correct that XP doesn't support SATA. But that doesn't mean that
you can't use SATA with XP, it means that the support for SATA has to
come from outside of XP.
 
S

Steve Hayes

Yes, it is true. Windows XP doesn't come with any SATA drivers and you
must (if you need them) install them in the very beginning of the
install by pressing F6 to install RAID, SATA, or any other device
driver(s) to work with Windows XP. And this is usually done by having
the driver(s) on a floppy disk. Yes an USB floppy drive will work too.
Strange.

I had XP installed on a machine with two IDE drives, and when I wanted toi
upgrade to a bigger one, I had to battle to find one, because they were all
selling SATA drives. Eventually I found one, but then other things started to
go wrong with the machine, do I bought a new one with two SATA drives.

I backed up the system on the old machine, restored it on the new one, and it
worked perfectly. So it must have SATA drivers somewhere to work with the SATA
drives. I didn't install a thing, just copied the whole lot.
 
B

BillW50

Strange.

I had XP installed on a machine with two IDE drives, and when I wanted toi
upgrade to a bigger one, I had to battle to find one, because they were all
selling SATA drives. Eventually I found one, but then other things started to
go wrong with the machine, do I bought a new one with two SATA drives.

I backed up the system on the old machine, restored it on the new one, and it
worked perfectly. So it must have SATA drivers somewhere to work with the SATA
drives. I didn't install a thing, just copied the whole lot.
There is a good reason for this. As "many SATA controllers offer
selectable modes of operation: legacy Parallel ATA emulation, standard
AHCI mode, or vendor-specific RAID... Legacy mode is a software
backward-compatibility mechanism intended to allow the SATA controller
to run in legacy operating systems which are not SATA-aware or where a
driver does not exist to make the operating system SATA-aware."

http://en.wikipedia.org/wiki/Advanced_Host_Controller_Interface

Thus if you are running your SATA controller in legacy mode, you don't
need a SATA driver. Although you also give up the advantages of AHCI.

And your claim that you copied Windows XP from one system and restored
on another system sounds very fishy if you ask me. As unless the two
systems are very much alike, it just won't work. As when Windows
installs, it loads the correct CPU, chipset, etc. drivers for that
machine. And moving it to another system, the odds are great that it
will be all wrong and it won't work at all.

There are ways to fix this. As sometimes a repair install can correct
this. And there are programs like Paragon Adaptive Restore that plugs in
all generic drivers which should work far better to make it runnable.
Then you allow Windows to detect all of the new devices to replace the
generic drivers.
 
Ad

Advertisements

B

BillW50

So does XP SP2.
Actually no they don't. At least not AHCI/SATA support anyway. If you
turn off AHCI in the BIOS, then you don't need a SATA driver. Although
to run the SATA controller in either AHCI or RAID mode, you need to
install a driver otherwise XP can't see it.

~~~~~~~~~~

Windows XP (and any OS older than Vista or linux kernel 2.6.19) does not
have came pre-packaged with driver to support AHCI/SATA mode, thus
creating a very common error that Wikipedia also described as "when
attempting to install Microsoft Windows XP or a previous version on an
AHCI-enabled system will cause the setup to fail with the error message
'set up could not detect hard disk drive…'".

http://www.mydigitallife.info/2007/10/23/windows-xp-setup-could-not-detect-and-find-any-sata-hard-disk-drive-on-ahci-mode/

~~~~~~~~~~
 
S

Steve Hayes

There is a good reason for this. As "many SATA controllers offer
selectable modes of operation: legacy Parallel ATA emulation, standard
AHCI mode, or vendor-specific RAID... Legacy mode is a software
backward-compatibility mechanism intended to allow the SATA controller
to run in legacy operating systems which are not SATA-aware or where a
driver does not exist to make the operating system SATA-aware."

http://en.wikipedia.org/wiki/Advanced_Host_Controller_Interface

Thus if you are running your SATA controller in legacy mode, you don't
need a SATA driver. Although you also give up the advantages of AHCI.
I didn't know that.

I thought that the drivers must have come in one of those automated updates.
And your claim that you copied Windows XP from one system and restored
on another system sounds very fishy if you ask me. As unless the two
systems are very much alike, it just won't work. As when Windows
installs, it loads the correct CPU, chipset, etc. drivers for that
machine. And moving it to another system, the odds are great that it
will be all wrong and it won't work at all.
Well, it did work. Windows detected new hardware the first time I ran it in
the new machine, and asked me to validate it or something.

Apart from the SATA drives, the other main difference was the new motherboard,
which is faster and had more memory. It also has speakers, which Windows
detected and installed something to make them work.

I'm typing this on it, and I've had it for about 6 months now.
 
B

BillW50

I didn't know that.

I thought that the drivers must have come in one of those automated updates.
Well if you need a SATA driver (this laptop don't sport a legacy
setting), then Windows XP won't see the drive at all.

If you set it to legacy mode and use Windows Updates, can you get the
SATA driver that way? I am not sure. And I can't test it here since all
of my computers doesn't have a legacy mode.
Well, it did work. Windows detected new hardware the first time I ran it in
the new machine, and asked me to validate it or something.

Apart from the SATA drives, the other main difference was the new motherboard,
which is faster and had more memory. It also has speakers, which Windows
detected and installed something to make them work.

I'm typing this on it, and I've had it for about 6 months now.
Well you lucked out then. It was close enough to the old system and it
worked. I have six M465 and the only difference is the CPU and memory
among them. Some are Celerons, Core Dual, or Core2 Dual.

And I swap the drives among them all of the time and Windows XP is ok
with it. Although one game doesn't like Core2 machines. As it refuses to
save and some graphics becomes corrupted. But it was installed on a
Celeron machine, so that might explain this problem.
 
Ad

Advertisements

Y

Yousuf Khan

Well, it did work. Windows detected new hardware the first time I ran it in
the new machine, and asked me to validate it or something.

Apart from the SATA drives, the other main difference was the new motherboard,
which is faster and had more memory. It also has speakers, which Windows
detected and installed something to make them work.

I'm typing this on it, and I've had it for about 6 months now.
Yes, it's true, sometimes wholesale major changes in components such as
the motherboard, processor, chipset, etc. can result in having nothing
more to do than boot into it, and it'll just redetect everything and
away you go. Maybe add some non-critical drivers downloaded from the
Internet or from a CD.

It is also true that sometimes just a minor component change can result
in all hell breaking loose and your system refuses to boot up anymore,
and you have to reinstall the OS from scratch. :)

Yousuf Khan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top