Promise Technologies Controller and W2K

  • Thread starter Thread starter dennis
  • Start date Start date
D

dennis

What would be the conflict between the Promise
Technologies 'Ultra.sys' driver and W2k-Pro returning the
codes 21,28 or 31 when a reinstall is attempted of this
driver?
Drivers from either the mb man. (ASUS) or from (Promise
Technologies) will not install and returns the error codes
noted above.
I am not booting from this IDE so it does not crash my
system, but I can no longer see the HDD connected to this
IDE channel.
Why does my op.sys. not recognise the supplied drivers,
when at one time it did?
Are there registry entries remaining from previously
installed drivers, if so, how does one safely remove them
or resolve this issue?
Microsoft's website does not offer anything related to
this problem other than getting the drivers from the OEM's
which I have done.
Getting any these SCSI drivers to function correctly on my
system has been a major problem (especially if one places
the op.sys. on the drive which boots from it. It has
crahed my system more than I care to recall. I now boot
from the drives on my primary IDE connectors that do not
use these drivers and have not had any problems since,...
until now.
Can anyone please help me with this.

Thks
Dennis
 
These may help.

CM_PROB_WILL_BE_REMOVED
Text that is displayed in Device Manager:

Windows is removing this device. (Code 21)
Close this dialog box, and then wait a few seconds. If this problem
continues, restart your computer.
Solution button: Restart Computer (restarts the computer)
Cause
The error message is self explanatory.
------------------------------------------------

CM_PROB_FAILED_INSTALL
Text that is displayed in Device Manager:

The drivers for this device are not installed. (Code 28)
Solution button: None
Cause
This error message generally indicates a bad driver .inf file or bad
hardware.
Troubleshooting
Verify that the driver you are using is digitally signed for Windows 2000.
If so, the driver may be bad and you should use normal corrupted file
procedures (try downloading an updated driver from the manufacturer's Web
site)..
Use appropriate hardware troubleshooting to verify the hardware integrity.
------------------------------------------------

CM_PROB_FAILED_ADD
Text that is displayed in Device Manager:

This device is not working properly because Windows cannot load the drivers
required for this device. (Code 31)
Solution button: None
Cause
This error message can occur for either of the following reasons:
If the operating system calls the driver's AddDevice routine and is
unsuccessful, or if the operating system fails to load a dependent device or
filter driver.
After unloading a driver, Windows 2000 did not close its handles, delete its
device names, and so on. From Object Manager's perspective, this indicates
that the old object/device never went away, so the system does not create a
device object for a device that reappears because of a possible object name
collision.
Troubleshooting
This behavior is usually caused by an issue in the device driver. Verify
that the driver you are using is digitally signed for Windows 2000. In the
second situation described above, the error message is resolved after you
restart the computer. To prevent this behavior from occurring again, obtain
a Windows 2000 signed driver from the device manufacturer.

If a dependent filter driver is not able to start, you can view the device
class key in the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class

Locate the device type that is reporting the error 31, and the view the
upper filter or lower filter entries. Make sure associated service entries
are located in the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services

You can either troubleshoot the dependent service or remove the offending
upper filter or lower filter entry from the class registry entry. For
example, the mouse reports an error 31, therefore, this is the mouse class
entry.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{4D36E96F-E325-11C
E-BFC1-08002BE10318}

upperfilters:RegMultiSz:mouclass OffendingDriver

You can either troubleshoot why the OffendingDriver does not start, or
remove the OffendingDriver entry from the upper filters, and then restart
the system.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect.


:
| What would be the conflict between the Promise
| Technologies 'Ultra.sys' driver and W2k-Pro returning the
| codes 21,28 or 31 when a reinstall is attempted of this
| driver?
| Drivers from either the mb man. (ASUS) or from (Promise
| Technologies) will not install and returns the error codes
| noted above.
| I am not booting from this IDE so it does not crash my
| system, but I can no longer see the HDD connected to this
| IDE channel.
| Why does my op.sys. not recognise the supplied drivers,
| when at one time it did?
| Are there registry entries remaining from previously
| installed drivers, if so, how does one safely remove them
| or resolve this issue?
| Microsoft's website does not offer anything related to
| this problem other than getting the drivers from the OEM's
| which I have done.
| Getting any these SCSI drivers to function correctly on my
| system has been a major problem (especially if one places
| the op.sys. on the drive which boots from it. It has
| crahed my system more than I care to recall. I now boot
| from the drives on my primary IDE connectors that do not
| use these drivers and have not had any problems since,...
| until now.
| Can anyone please help me with this.
|
| Thks
| Dennis
|
|
|
|
 
Back
Top