masss storage controller

  • Thread starter Thread starter Dennis
  • Start date Start date
D

Dennis

Is there a WHQL driver for the 'Promise Technologies'
chipset for the PCI-Ultra ATA 100 controllers on the
A7V133A ASUS motherboards?
I am using W2K pro. SP4 and had the 'WinXP Promise Ultra
100 IDE controller' driver ver. 2.0.0.39 installed which
at the time in the device manager indicated it was
digitally signed by Microsoft.
I tried to install a more recent or correct version like
the 'Win2000 Promise Ultra 100 controller' ver. 2.0.0.49
which I thought would be the proper one due to the
operating system I was running.
After uninstalling the previous driver and trying to
installing the latter, it has not been successful because
the system repeatedly states a code 31 (driver not found)
everytime I do so.
Every attempt at installation (even with the previous
driver that worked fine) W2K fails to install
the 'ultra.sys' driver and says that the device is not
working correctly, which then will not show my devices
installed on that IDE bus.
How and why did the previous driver indicate that it was
WHQL when it was not a digitally signed driver for windows
originally?
I am uninstalling and installing the drivers correctly,
but I am totally confused as to why this is happening.
I Would greatly appreciate somones assistance in this
matter.

Thks

Dennis
 
David:
Yes I agree with your comment, but the driver from the
ASUS websit Ver. 2.00.29. for this mb will notinstall
also. It returns " The drivers for this device are not
installed. (Code 28), You need to restart your computer
before the changes you made to this device will take
affect".
I also have gotten a code 31 during one of the other
driver installs indicating, "A driver for this device was
not required, and has been turned off"
Restarting or reinstaling does not work, PNP still wants
to have a device driver for the Mass Storage Controller it
finds.
Is there a windows registry entry that still exists that
might be preventing me from completing this task?
I believe the problem is with windows not the drivers.
Do you know what that may be, and the solution to it?

Rgds.

Dennis
 
Back
Top