108
•
Troubleshooting
Keithley DAS-1700 Series
8.
The General tab will show the reason why the driver did not load.
9.
The Resources tab will show if Windows detected an unresolvable
hardware conflict.
Getting More Driver Information on Windows NT
On Windows NT, the only reasons that a driver does not load are
•
You did not install the driver software.
•
You did not correctly configure the driver.
•
You changed the driver startup parameters.
An incorrectly configured driver will report the reasons that it failed to load into the
Windows Event Log. See “Checking for Device Errors” on page 107 for more
information.
On Windows NT, DriverLINX drivers load automatically during system boot. An
administrator can change the startup command for any NT driver to either “manual”
or “disabled”.
1.
Run “DriverLINX Configuration” from Windows Control Panel.
2.
Select the “DriverLINX” tab.
3.
Click the “+” icon next to DriverLINX to expand the list of drivers, if
necessary.
4.
Select “Keithley DAS-1700”. Click “+”, if necessary, to expand the list.
5.
Select the line with the number of the Logical Device that did not load.
6.
Right click the mouse to see a popup menu.
7.
Select “Automatic” to instruct Windows to load the driver the next time
you reboot.
StockCheck.com