P
pjgtech
Right, over the last six weeks or so, my pc has twice refused to start,
usually giving a "Windows system file is missing" message.
I think I have narrowed the problem down to the SATA drivers for my Serial
ATA hard disk (Maxtor 120Gb).
Somehow Windows "loses" the SATA controller info, and cannot recogniose
the hard disk and therefore cannot load windows, hence the error message.
I have to manually reload the SATA controller driver by re-starting the
pc, pressing Del to get into the bios, set the floppy drive to be first
device loaded (hard disk is usually first).
Restart the pc and put the SATA drive disk into the floppy drive, when the
pc starts note the message which says "press F6 during boot up to load
raid/scsi drivers" and press F6. Load the SATA driver and windows starts
ok.
I did this the first time it happened about six weeks ago. Everything was
then fine for a few weeks, and then it happened again.
So now I'm getting paranoid about the hard drive (what with SATA being
fairly new technology and all?)
So I decide to buy a new SATA drive (need more space anyway) this time I
buy a Samsung (eg: not Maxtor) SATA 120Gb drive and install it ok, and
again install the SATA driver via the F6 option at start up and windows
loads ok and everything is working ok again.
Then this week, the same thing happens, windows "loses" the SATA
controller info and I have to re-install the driver at the F6 prompt yet
again.
Now, I think this cannot be a problem with the hard disk (not *both* of
them?) but could it be a m/b problem? The m/b is not losing the time or
anything else, so I don't think its the cmos battery.
Regarding SATA drives, I am aware that there may be a problem with NForce
chipsets that has been fixed with BIOS updates.
But my m/b is a Asus A7N8X Deluxe nForce2, eg: not the older vanilla
nForce chipset (nb: this board is Rev 2.0). I have trawled the Asus
website but found no further info on this, but I have updated the m/b bios
anyway (from v1004 to v1007).
Anyone else have any more info on this, like what might be causing the
SATA controller driver loss? or a cure for it/
Thanx (posted elsewhere so sorry if you see this more than once!)
Peter
*Peter* - http://www.cix.co.uk/~pjgtech/home.html
usually giving a "Windows system file is missing" message.
I think I have narrowed the problem down to the SATA drivers for my Serial
ATA hard disk (Maxtor 120Gb).
Somehow Windows "loses" the SATA controller info, and cannot recogniose
the hard disk and therefore cannot load windows, hence the error message.
I have to manually reload the SATA controller driver by re-starting the
pc, pressing Del to get into the bios, set the floppy drive to be first
device loaded (hard disk is usually first).
Restart the pc and put the SATA drive disk into the floppy drive, when the
pc starts note the message which says "press F6 during boot up to load
raid/scsi drivers" and press F6. Load the SATA driver and windows starts
ok.
I did this the first time it happened about six weeks ago. Everything was
then fine for a few weeks, and then it happened again.
So now I'm getting paranoid about the hard drive (what with SATA being
fairly new technology and all?)
So I decide to buy a new SATA drive (need more space anyway) this time I
buy a Samsung (eg: not Maxtor) SATA 120Gb drive and install it ok, and
again install the SATA driver via the F6 option at start up and windows
loads ok and everything is working ok again.
Then this week, the same thing happens, windows "loses" the SATA
controller info and I have to re-install the driver at the F6 prompt yet
again.
Now, I think this cannot be a problem with the hard disk (not *both* of
them?) but could it be a m/b problem? The m/b is not losing the time or
anything else, so I don't think its the cmos battery.
Regarding SATA drives, I am aware that there may be a problem with NForce
chipsets that has been fixed with BIOS updates.
But my m/b is a Asus A7N8X Deluxe nForce2, eg: not the older vanilla
nForce chipset (nb: this board is Rev 2.0). I have trawled the Asus
website but found no further info on this, but I have updated the m/b bios
anyway (from v1004 to v1007).
Anyone else have any more info on this, like what might be causing the
SATA controller driver loss? or a cure for it/
Thanx (posted elsewhere so sorry if you see this more than once!)
Peter
*Peter* - http://www.cix.co.uk/~pjgtech/home.html