Question Regarding My SATA DVD Burner

[gecko]

I bought a SATA DVD burner drive by mistake a while back. It had a
good price, and I missed the fact that it was SATA. Since my MOBO has
SATA I installed it and have been using it, with no problems.

Then, I wanted to install XP on a new boot hard drive, and discovered
that at the end of the 'load phase' at the beginning of the
installation, I got an error which said that a drive had errors
requiring the running of CHKDSK. I assumed it was talking about the
new hard drive, so I tried another - same error. Luckily, I had a
spare IDE burner, so I tried the installation, using that - and it
worked just fine.

When I got to the point of installing MOBO drivers/software, long
after completion of the XP installation, I noticed that one of the
drivers wanted was for SATA. This got me to thinking - if the SATA
capability requires drivers, then how could the SATA drive ever be
used to provide the XP installation disk?

What am I missing here?

Thanks

-GECKO

 

[Grinder]

I bought a SATA DVD burner drive by mistake a while back. It had a
good price, and I missed the fact that it was SATA. Since my MOBO has
SATA I installed it and have been using it, with no problems.

Then, I wanted to install XP on a new boot hard drive, and discovered
that at the end of the 'load phase' at the beginning of the
installation, I got an error which said that a drive had errors
requiring the running of CHKDSK. I assumed it was talking about the
new hard drive, so I tried another - same error. Luckily, I had a
spare IDE burner, so I tried the installation, using that - and it
worked just fine.

When I got to the point of installing MOBO drivers/software, long
after completion of the XP installation, I noticed that one of the
drivers wanted was for SATA. This got me to thinking - if the SATA
capability requires drivers, then how could the SATA drive ever be
used to provide the XP installation disk?

What am I missing here?

There is a point early in the installation where the status at the
bottom of the screen says "Press F8 to install third-party drivers," or
something similar. If you have the drivers on a floppy, you can serve
them up.

I'm not sure that will fix your problem. It might be that giving the
proper drivers for the CD-ROM *after* you have booted a disc from it
might not immediately update the drivers in use. Still, it's worth a try.

 

[GlowingBlueMist]

I bought a SATA DVD burner drive by mistake a while back. It had a
good price, and I missed the fact that it was SATA. Since my MOBO has
SATA I installed it and have been using it, with no problems.

Then, I wanted to install XP on a new boot hard drive, and discovered
that at the end of the 'load phase' at the beginning of the
installation, I got an error which said that a drive had errors
requiring the running of CHKDSK. I assumed it was talking about the
new hard drive, so I tried another - same error. Luckily, I had a
spare IDE burner, so I tried the installation, using that - and it
worked just fine.

When I got to the point of installing MOBO drivers/software, long
after completion of the XP installation, I noticed that one of the
drivers wanted was for SATA. This got me to thinking - if the SATA
capability requires drivers, then how could the SATA drive ever be
used to provide the XP installation disk?

What am I missing here?

Thanks

-GECKO

Some motherboards provide minimum native SATA capabilities which would allow
the installation of the OS from a SATA drive.

What causes problems is that many SATA devices need special drivers to fully
utilize their many features. At the end Windows tries to activate or test
the device to check on the capabilities but without the drivers provided by
the manufacturer the test fails.

It could be something as similar to the drive responding to the final
Windows test with "I have feature "X" but do not understand your command to
activate it." Install the actual manufacturers SATA drivers and then both
Windows and the device should be able to fully communicate with each other.

 

[gecko]

Some motherboards provide minimum native SATA capabilities which would allow
the installation of the OS from a SATA drive.

What causes problems is that many SATA devices need special drivers to fully
utilize their many features. At the end Windows tries to activate or test
the device to check on the capabilities but without the drivers provided by
the manufacturer the test fails.

It could be something as similar to the drive responding to the final
Windows test with "I have feature "X" but do not understand your command to
activate it." Install the actual manufacturers SATA drivers and then both
Windows and the device should be able to fully communicate with each other.

Thanks for responses.

SATA drivers are included on a CD that accompanied the MOBO some time
ago. I guess I could try to copy just them from the CD to a floppy,
assuming they would fit. I don't remember a CD coming with the drive
itself. I'll have to look in my closet more carefully.

Maybe the BIOS addresses SATA. I'll look there also.

-GECKO

 

[gecko]

Some motherboards provide minimum native SATA capabilities which would allow
the installation of the OS from a SATA drive.

What causes problems is that many SATA devices need special drivers to fully
utilize their many features. At the end Windows tries to activate or test
the device to check on the capabilities but without the drivers provided by
the manufacturer the test fails.

It could be something as similar to the drive responding to the final
Windows test with "I have feature "X" but do not understand your command to
activate it." Install the actual manufacturers SATA drivers and then both
Windows and the device should be able to fully communicate with each other.

I checked. I can't isolate any SATA drivers on the MOBO installation
CD, even though the menu thereon specifies SATA as part of the setup.

The BIOS does address SATA and is set up to allow bootup from SATA. I
guess that is how it did start the boot from the CD. It failed as
soon as the preliminary loading of files was done - before any XP
installation choices occur.

As I said, the error persisted for two different hard drives, and
went away as soon as I used a PATA CD drive instead of the SATA CD
drive. I was assuming that the error was for the hard drive being
used, but maybe not. Maybe the error was for the SATA drive. It said
I needed to run CHKDSK.

Thanks again

-GECKO

 

[Phil]

I bought a SATA DVD burner drive by mistake a while back. It had a
good price, and I missed the fact that it was SATA. Since my MOBO has
SATA I installed it and have been using it, with no problems.

Then, I wanted to install XP on a new boot hard drive, and discovered
that at the end of the 'load phase' at the beginning of the
installation, I got an error which said that a drive had errors
requiring the running of CHKDSK. I assumed it was talking about the
new hard drive, so I tried another - same error. Luckily, I had a
spare IDE burner, so I tried the installation, using that - and it
worked just fine.

When I got to the point of installing MOBO drivers/software, long
after completion of the XP installation, I noticed that one of the
drivers wanted was for SATA. This got me to thinking - if the SATA
capability requires drivers, then how could the SATA drive ever be
used to provide the XP installation disk?

What am I missing here?

Thanks

-GECKO

I had the same problem with an Intel board -- with the added annoyance that the
board doesn't have floppy drive support. In spite of this, Intel helpfully
supply the SATA drivers on a floppy disk...

The problem arises, as I understand it, when the BIOS hands over to the OS at
the end of the first stage of installation. Using a PATA CD dive allowed the
system to boot fully from the CD, but without the SATA drivers I still couldn't
see the HDDs.

This article

http://www.msfn.org/board/Integration-Intel-Sata-t107504.html

helped me to sort it out. It's about the Intel controllers specifically, but a
great deal of the info is more generally applicable.


Phil

 

[gecko]

I had the same problem with an Intel board -- with the added annoyance that the
board doesn't have floppy drive support. In spite of this, Intel helpfully
supply the SATA drivers on a floppy disk...

The problem arises, as I understand it, when the BIOS hands over to the OS at
the end of the first stage of installation. Using a PATA CD dive allowed the
system to boot fully from the CD, but without the SATA drivers I still couldn't
see the HDDs.

This article

http://www.msfn.org/board/Integration-Intel-Sata-t107504.html

helped me to sort it out. It's about the Intel controllers specifically, but a
great deal of the info is more generally applicable.


Phil

Thanks Phil