- #If you use the system configuration utility install#
- #If you use the system configuration utility drivers#
- #If you use the system configuration utility update#
- #If you use the system configuration utility driver#
- #If you use the system configuration utility series#
The Resources tab (on the device’s properties sheet) allows you to manually adjust the device’s settings. If there was a conflict, you’d see a message that said something like, “IRQ 11 is conflicting with a network card.” You can also see that Windows says that the card is not conflicting with any other devices. For example, in Figure C, you can see that my NIC card is using IRQ 11 and view the card’s input/output ranges. If the device is malfunctioning, you can usually get some type of information about where the problem is located from the Resources tab. The Resources tab is where you can look to see what resources that the device is actually using.
#If you use the system configuration utility update#
There’s also a button on the tab you can use to update the driver.
#If you use the system configuration utility drivers#
The Drivers tab is used for viewing a driver’s manufacturer, version, or date.
#If you use the system configuration utility driver#
Most of the devices in your system will also have a Driver tab and a Resources tab on their properties sheets. This tab also contains two check boxes that you can use to disable the device. The General tab displays a summary of whether or not the device is working properly (as far as Windows can tell). By default, the properties sheet’s General tab is selected. Select a malfunctioning device and click the Properties button. With that said, let’s take a look at the anatomy of a malfunctioning device. One other possibility is that someone could have incorrectly assigned resources to one of the two devices manually.
![if you use the system configuration utility if you use the system configuration utility](https://people.richland.edu/dkirby/172sysedit_files/image002.gif)
Another possibility is the video driver somehow interferes with the network card’s driver. For example, the video card could be physically occupying a resource, such as an IRQ or a base memory address, that the network card needs. There are several ways this situation could happen. However, if you’ve checked out the system and can’t find anything wrong with the network card, then maybe another component, such as the video card, might be causing the problem. Most of the time, the network card will be the source of the problem. For example, suppose the Device Manager shows a network card malfunctioning. Another inaccuracy may occur if a device malfunctions, but the failure is a result of another malfunctioning device that the Device Manager doesn’t display. Occasionally, a device will malfunction, but because of the type of malfunction, the Device Manager will not recognize that a problem exists.
![if you use the system configuration utility if you use the system configuration utility](https://www.howtogeek.com/wp-content/uploads/2013/05/tpt_top_a.png)
One word of caution: Although I mentioned that the Device Manager indicates malfunctioning devices, it is not necessarily 100 percent accurate. The Device Manager highlights disabled and malfunctioning drivers.
#If you use the system configuration utility series#
In that instance, the third article in this series will be more beneficial to you in finding and fixing your problem. Should the problem with your device go away, then the trouble lies somewhere within the real mode. If it does, reenable the Config.sys and Autoexec.bat files and continue with the troubleshooting process. Then, reboot your machine and see if the problem still exists. Simply disable Config.sys and Autoexec.bat as shown in Figure A, and click OK. When you do, you’ll be able to select the files that are processed during the boot process. On the General tab, select the Selective Startup radio button. The easiest way to temporarily disable these commands is to open the Microsoft System Information utility and then select the System Configuration Utility from the Tools menu. Sometimes totally unrelated devices can cause problems with each other when device drivers or memory managers are loaded in real mode. When you disable the commands, you’re ensuring that nothing you’ve loaded in real mode will be adversely affecting protected mode. Before beginning the troubleshooting process, you should also temporarily disable any commands in your Config.sys or Autoexec.bat files. In this article, I’m assuming that you’ve already done that.
#If you use the system configuration utility install#
In part one, I told you to first download and install new device drivers for the malfunctioning hardware. If you’re still depending on real mode drivers and are having trouble with your system, then you’ll be happy to know that part three will be dedicated to troubleshooting real mode drivers.īefore we get started with the troubleshooting process, let’s go over a few things. In this article, I’ll discuss some techniques you can use to troubleshoot protected mode drivers.
![if you use the system configuration utility if you use the system configuration utility](https://i.ytimg.com/vi/zz30zAnRx8A/mqdefault.jpg)
In that article, I explained how Windows tends to function much better with protected mode drivers than it does with real mode drivers. In part one of this series, I explained the differences between real mode and protected mode drivers.
![if you use the system configuration utility if you use the system configuration utility](https://warp9td.com/images/Documentation/SCU/Images/EasyMode_04.png)
Get IT Done: Using the System Configuration Utility to troubleshoot real mode and protected mode driversĭiscover how a problem can stem from a malfunctioning device thats different from the one indicated by Microsofts Device Manager.