A7V266-E Promise problem resolved!

  • Thread starter Thread starter Andy M Moore
  • Start date Start date
For any of you who have not upgraded to an A7Nxxx and are still on
A7V266-E, maybe you've encountered the problem I did ages ago. You
downloaded the Promise Build 39 driver, from ASUS.de, from ASUS.tw, and
eventually from the US (when it would appear). It installed just fine,
but then, when you tried to apply W2KSP3 (or later, SP4), you got a BSOD
on a bum driver.

Well, I finally hit the wall this weekend when I installed an app that
required SP3 or greater. I went to the Promise.com site, and even
though they warn you to download only from your motherboard manufacturer
site, I downloaded Build 39 from their site. It took a modification to
TXTSETUP.OEM for the install to select WIN2000 (the default is WIN XP),
but it installed just fine, and the BSOD is gone. Hooray for perseverance.

KPR
 
Oh, and one more thing... the note on Build 39 at the Promise.com site says:

"Fixes problem with W2KSP3".

KPR
 
Oh, and one more thing... the note on Build 39 at the Promise.com site says:

"Fixes problem with W2KSP3".

KPR
 
KPR said:
For any of you who have not upgraded to an A7Nxxx and are still on
A7V266-E, maybe you've encountered the problem I did ages ago. You
downloaded the Promise Build 39 driver, from ASUS.de, from ASUS.tw, and
eventually from the US (when it would appear). It installed just fine,
but then, when you tried to apply W2KSP3 (or later, SP4), you got a BSOD
on a bum driver.

Well, I finally hit the wall this weekend when I installed an app that
required SP3 or greater. I went to the Promise.com site, and even
though they warn you to download only from your motherboard manufacturer
site, I downloaded Build 39 from their site. It took a modification to
TXTSETUP.OEM for the install to select WIN2000 (the default is WIN XP),
but it installed just fine, and the BSOD is gone. Hooray for perseverance.

KPR
Click to expand...

Are you talking about the stop error with the scsiport.sys file? After
reloading Win2000, then applying SP3,
I then replaced the scsiport.sys file with the older version. Work fine. I
never had a problem with SP4.
 
I am glad that you found a solution that satisfied you. My observation
is that it was unknown whether the error was in the driver or
scsiport.sys. Replacing an old version of scsiport.sys didn't answer
that question, and perhaps left open another vulnerability. Now,
Promise finally takes the blame for their faulty driver, and nothing
ever was bad in scsiport.sys.

In a business environment, management wants to know with proof who was
at fault. I think it's a matter of training.

KPR
 
I am glad that you found a solution that satisfied you. My observation
is that it was unknown whether the error was in the driver or
scsiport.sys. Replacing an old version of scsiport.sys didn't answer
that question, and perhaps left open another vulnerability. Now,
Promise finally takes the blame for their faulty driver, and nothing
ever was bad in scsiport.sys.

In a business environment, management wants to know with proof who was
at fault. I think it's a matter of training.

KPR
 
Back
Top