mismatched BIOS and Windows XP highpoint driver

[David Shorthouse]

Hello folks,

I have an IT7 original board with D7 BIOS (Highpoint 374 version 1.22) and for the longest time was safely running the 1.22a Highpoint driver in Windows XP SP1. Now it seems Microsoft has released a USB 1.1 and 2.0 power management patch both on its own as a recommended update and now embedded in a recent roll-up. This patch wreaked havoc on the Highpoint controller once causing a temporary loss of the array until reboot. This problem only appeared upon resume from suspend to RAM, which I use religiously.

Being stuck with this XP roll-up without any way to go back to the original USB drivers to fix this potentially deadly Highpoint controller issue, I tried installing the 1.23 version of the Highpoint driver even though it doesn't match the version in the BIOS. I noticed a drop in throughput because of this upgrade, but the issue I was having before disappeared. Is there any danger to using the 1.23 Windows XP Highpoint driver set with a 1.22 BIOS set? If so, has anyone patched the 1.23 into the Highpoint BIOS? Do I have to rebuild the RAID0 array if I flash to this version? Please point me to where I can find this BIOS flash if you recommend that I use it.

Thanks for any advice,

Dave

 

[0_Qed]

David,

Altho of 'little/no/none/nada' help ... a =great= write_up.

I dont have an/some/any answer to your quandry ...
just a few <?>, interspersed below ,
and, a skosh of moral support.

I have an IT7 original board with D7 BIOS (Highpoint 374 version 1.22) and for the longest time was safely running the 1.22a Highpoint driver in Windows XP SP1. Now it seems Microsoft has released a USB 1.1 and 2.0 power management patch both on its own as a recommended update and now embedded in a recent roll-up. This patch wreaked havoc on the Highpoint controller once causing a temporary loss of the array until reboot. This problem only appeared upon resume from suspend to RAM, which I use religiously.

Q1 - Any idea what PCI "int(s)" the USB, & HiPt, devices are located upon ??

Q2 - Any chance you can recover/mooch the older USB drivers ...

Being stuck with this XP roll-up without any way to go back to the original USB drivers to fix this potentially deadly Highpoint controller issue, I tried installing the 1.23 version of the Highpoint driver even though it doesn't match the version in the BIOS. I noticed a drop in throughput because of this upgrade, but the issue I was having before disappeared.

I 'read' above to mean that :
(1) you installed(overlaid) :
. 1.23 version of the Highpoint driver
. using the D7 BIOS (Highpoint 374 version 1.22)
and ...
(2) that the 'array loss', upon mem_suspend, went away .

Y/N ????

Is there any danger to using the 1.23 Windows XP Highpoint driver set with a 1.22 BIOS set?

A =fair= <?> ... dunno , at =all=.

I have a =dim= recall that "a" bios|drvr mismatch has been used before( old NG posts ) BUT not at all =sure= of the mentioned, precise configuration of such mismatch, and ... ??thimk?? it read as "not a problem" ... again, a =dim= recall.

ping ==> TomG

If so, has anyone patched the 1.23 into the Highpoint BIOS?

?? HP 1.23 ==patched==> D7 bios ???
dunno ...
TomG mite know ,
probably hes already done it, and/or has it on his FTP server .

Do I have to rebuild the RAID0 array if I flash to this version?

A =fair= <?> ... dunno , at =all=.

Please point me to where I can find this BIOS flash if you recommend that I use it.

TomG is a source for this "one" ... I'd thimk ...
unless you wanna bash it.

Thanks for any advice,

I suppose 'straws' look good if you're 3' below the surface, downward bound. <gallows humor>

Hopefully you've a Bios Savour ... backup for your data. Just now 'lit' my virt_candle for you ... =good= luck.

A well done "problem ID" ...
now, ....
onward to the solution.

Qed.

 

[David Shorthouse]

Thanks for the comments.

The Highpoint controllers are on their own IRQ and are not sharing with anything else, including the USB IRQ, so that rules out any conflict in that regard.

I suppose I could roll the USB drivers back to their pre-patched version, but now I am beginning to wonder if the "fix" for this problem is to just re-install the 1.22a driver version over itself, assuming there was just a re-enumeration problem upon resume from STR.

But, I think I'll just stick with the 1.23 and maintain my mismatched OS and BIOS versions. I can live with the marginal drop in throughput if it means a safer environment.

I do seem to recall that someone has streamed the 1.23 driver into the IT7 BIOS, but that a RAID0 rebuild is necessary after the flash.

David,

Altho of 'little/no/none/nada' help ... a =great= write_up.

I dont have an/some/any answer to your quandry ...
just a few <?>, interspersed below ,
and, a skosh of moral support.

I have an IT7 original board with D7 BIOS (Highpoint 374 version

1.22)

and for the longest time was safely running the 1.22a Highpoint driver

in

Windows XP SP1. Now it seems Microsoft has released a USB 1.1 and 2.0 power management patch both on its own as a recommended update and now embedded in a recent roll-up. This patch wreaked havoc on the Highpoint controller once causing a temporary loss of the array until reboot. This problem only
appeared upon resume from suspend to RAM, which I use religiously.

Q1 - Any idea what PCI "int(s)" the USB, & HiPt, devices are located upon ??

Q2 - Any chance you can recover/mooch the older USB drivers ...

Being stuck with this XP roll-up without any way to go back to the
original USB drivers to fix this potentially deadly Highpoint controller
issue, I tried installing the 1.23 version of the Highpoint driver even ...

Not quite. Sorry I wasn't clear. The current IT7 BIOS has the Highpoint HPT374 driver 1.22, but I went to the Highpoint web site and downloaded the
1.23 version to install in Windows XP SP1a's SCSI controller. Indeed, upon installation (overlay/upgrade) the disk read/write and otherwise temporary broken RAID0 upon resume from suspend to RAM disappeared.

Is there any danger to using the 1.23 Windows XP Highpoint
driver set with a 1.22 BIOS set?

A =fair= <?> ... dunno , at =all=.

I have a =dim= recall that "a" bios|drvr mismatch has been used before( old NG posts ) BUT not at all =sure= of the mentioned, precise configuration of such mismatch, and ... ??thimk?? it read as "not a problem" ... again, a =dim= recall.

...

Haven't got a BIOS Saviour...probably should look into one if I proceed with this any further and especially if Microsoft releases their own drivers that conflict with 3rd party critical devices.

A well done "problem ID" ...
now, ....
onward to the solution.

Qed.

 

[0_Qed]

David Shorthouse wrote:

Thanks for the comments.

"You" earn what you get ...

The Highpoint controllers are on their own IRQ and are not sharing with anything else, including the USB IRQ, so that rules out any conflict in that regard.

I suppose I could roll the USB drivers back to their pre-patched version, but now I am beginning to wonder if the "fix" for this problem is to just re-install the 1.22a driver version over itself, assuming there was just a re-enumeration problem upon resume from STR.

But, I think I'll just stick with the 1.23 and maintain my mismatched OS and BIOS versions. I can live with the marginal drop in throughput if it means a safer environment. ...