I have an ECS P6VEM mainboard (socket 370, Via VT133 chipset) with a 60
GB Maxtor DM+9 as primary master, and an 80 GB DM+9 as primary slave.
The 80 GB drive was showing very poor write performance, so I downloaded
the IBM/Hitachi feature tool, which revealed that the drive's write
cache was disabled. I used the tool to enable the write cache, but after
the next reboot the write cache was disabled again. There is nothing in
the BIOS to enable/disable the write cache, and the drive is identified
as an ATA-100 drive. Any suggestions why the write cache will not stay
enabled?

Thanks,
Peter

"kalabp" <kalabp@netscape.net> wrote in message news:6p5pc.78950$FH5.1782424@news20.bellglobal.com ...
Reboot into what?

Folkert Rienstra wrote:
Utilising ones brain might suggest this is Windows 2000 Server, since this
is normal for a system running Active Directory.
His user-agent string also suggests Windows 2000.

wake the fuck up.

"Carl Farrington" <carl@000compsup000.net.invalid> wrote in message
news:c84f0u$1q4$1
I'd prefer if he didn't.

--
Joep

Carl Farrington wrote:
Basically all I did was this:
- boot from the feature tool diskette.
- observe that the disk's write cache is disabled.
- use the feature tool to enable the write cache, tool says "ok" and
shows write cache now enabled.
- reboot from the feature tool diskette.
- observe that the write cache is disabled again.
Actually Win2K Pro, but since it has a setting to enable the write cache
from the device manager the disk behaves as expected. This is the same
drive that was showing very poor performance when I put it into an
external USB 2.0 case; I guess now I know why.

I also assume that at this stage the drive is basically defective,
though being beyond its 1 year warranty I equally assume that I'm stuck
with it.

Cheers

"kalabp" <kalabp@netscape.net> wrote in message news:196qc.9421$325.491441@news20.bellglobal.com
Right, so it is not the OS that is setting it back, which is why I asked.

So the drive looses it's setting just by a reset alone. If this were to be
an IBM then this might indicate that the drive had used up all its spare
sectors. Unfortunately the Maxtor manual doesn't say anything about it.

Assume all you want. If you care, you check.

"Carl Farrington" <carl@000compsup000.net.invalid> wrote in message news:c84f0u$1q4$1$8300dec7@news.demon.co.uk
Now, who is the one looking braindead with egg in his face?