Service Pack 3 corrupts HPT366 drivers?

[eljar]

I recently installed Win2K, and upgraded it to SP2.
This seemed to work fine. No probs at all.
Now, after I installed SP3 everything seems okay, but as soon
as I strain the disks on the HPT-controller, Windows goes BSOD
with the message IRQL_NOT_LESS_OR_EQUAL.
My driver version is 1.25.0.10

Unfourtunatly I didn't leave the option of uninstalling the SP, so
know I'm desperate for another solution. Does anyone
know which files that the HPT-driver relies on or who knows about a fix?

Thanks.
Oh, the specs.. BP2 Dual Cel533 with NJ bios.

[hyperspace]

Have you tried using the RU version of the BIOS?

[Homer S.]

Please hyperspace, just a question:

when you told us about using RU BIOS, did you mean you upgraded successfully to SP3 without having any trouble with HPT366 drivers (and you're using RU, of course), or was it just a suggestion for a try?

As I'm about to upgrade to SP3 myself (:arrow: I'm RU-based), I'd like to know if I can do it: I'd rather not crash my Win2K .

Thanks!

[eljar]

After removing one of the disks (it started to go "Ziong-dunk-dunk..")
the problem became much less frequent. It still happens but know it's only
once in a while. Anyway it runs satisfactory, since my main OS is Linux,
and I don't care to reboot very often..

[eljar]

I installed W2K and SP1 using the HPT366 driver diskette
during setup of W2K.

After upgrading to SP3 the "hpt366.sys" file in
"c:\winnt\system32\drivers", was changed from the
version included with the hpt-driver: 5.0.2195.1
to some weird version probably included with sp3
with version number: 4.0.1381.1
Also the original driver states it's target product is:
"Windows (R) 2000 DDK driver"
and the "fake" that didn't work claims it is:
"Microsoft(R) Windows NT(TM) Operating System"
I simply copied the file from the hpt-driver over the
other file (while booted from the on-board ide).

So now it's running stable again.

[InactiveX]

(it started to go "Ziong-dunk-dunk..")

Beware - this is a sign that the HPT3666 could be causing permanent damage to your hard disk.

The faulty HPT is the reason many of us, myself included, avoid that controller like the plague. I've replaced it with a Promise ATA/100 controller.

[eljar]

Thanks for the warning.

I don't know if there's been any resarch into the HPT366 controller but
my harddisk/HPT controller performs very diffrently in windows and in
linux. I run W2K without ACPI, and every time I reboot the system from
W2K it shuts down(spin down) the disk in a manner that dosn't sound healthy.
And the disk won't spin up again until the HPT is re-initialized after POST.

This never occurs under linux. No bad sounds at all.
Is there any indication that the drive-trashing may be a driver issue?

[eljar]

Double posting? oh, well..

[hyperspace]

Have you tried the RU BIOS version for the BP6?

[hyperspace]

Please hyperspace, just a question:

when you told us about using RU BIOS, did you mean you upgraded successfully to SP3 without having any trouble with HPT366 drivers (and you're using RU, of course), or was it just a suggestion for a try?

As I'm about to upgrade to SP3 myself (:arrow: I'm RU-based), I'd like to know if I can do it: I'd rather not crash my Win2K .

Thanks!

Sorry. Using the RU BIOS revision, in regard to the issues with the HPT366 controller. I have been using SP3 since it came out with either HPT366 driver revision, 1.25.0.1 or 1.25.0.2. Using RU.

[Homer S.]

Sorry. Using the RU BIOS revision, in regard to the issues with the HPT366 controller. I have been using SP3 since it came out with either HPT366 driver revision, 1.25.0.1 or 1.25.0.2. Using RU.

Thanks for your answer.
BTW, I've already upgraded both to SP3, and further on to SP4 recently, with no apparent trouble as for now. I'll see if it's going fine or not, at least until I ultimately migrate to Linux