Professional Web Hosting, Perl Scripting And Developing Blog

Managing and Troubleshooting Hardware Chapter 13 Figure 13-9. View resources by type or resources by connection to check resource settings in Device Manager. Another way to check for conflicts is to use the System Information utility (Msinfo32.exe). Start the System Information utility by clicking Programs or All Programs, Accessories, System Tools, and then System Information. In System Information, expand Hardware Resources, and then select Conflicts/Sharing. As shown in Figure 13-10, a list of all resources that are in use is displayed. Again, keep in mind that devices can share IRQ settings thanks to ACPI, so what you are looking for are two unrelated devices sharing the same memory addresses or I/O ports, which would cause a conflict. Keep in mind related devices can share memory addresses and I/O ports. In the example, the Standard VGA Graphics Adapter and the Intel 82845 Processor to AGP Controller share the same memory addresses and I/O ports. That s okay because they are related. The PCI Bus is using a memory address space with these devices as well, which is as it should be because Standard VGA Graphics Adapter and the Intel 82845 Processor to AGP Controller are both PCI devices. 405 Part 4: Managing Windows Server 2003 Systems
Check Tomcat Web Hosting services for best quality webspace to host your web application.

Microsoft Windows Server 2003 Inside Out Chapter 13 If the suggested action doesn t resolve the problem, you might be able to use the Hardware Troubleshooter to resolve the problem. Double-click the device in Device Manager, then click Troubleshoot in the General tab. Keep in mind that if the device drivers aren t installed properly, you won t have a Troubleshoot option. Instead, you ll have a Reinstall Driver button. Clicking Reinstall Driver starts the Hardware Update Wizard discussed in the section entitled Updating a Device Driver earlier in this chapter. Resolving Resource Conflicts Anyone who remembers IRQ conflicts will be thankful that current computers support ACPI BIOS. With ACPI BIOS, resources are allocated automatically by the operating system at startup, and multiple devices can share the same IRQ settings. These changes mean IRQ conflicts are largely a thing of the past. However, ACPI depends on Plug and Play, and devices that are not fully compatible can sometimes cause problems, particularly ISA devices. Troubleshooting Check the device slot configuration Some conflicts occur because PCI interrupts are sharable, while ISA interrupts are nonsharable. Typically, this is a BIOS problem. If a device is in a PCI slot but the slot is configured in BIOS as reserved for ISA, a conflict can occur. You must change the BIOS settings rather than the resource configuration to resolve the problem. If you suspect a device conflict is causing a problem with the current device, check the Conflicting Device list in the lower portion of the Resources tab. It will either list No Conflicts or the specific source of a known conflict. In Device Manager, you can quickly check resource allocations by choosing Resources By Type or Resources By Connection on the View menu. In Figure 13-9, both ISA and PCI devices are using IRQ settings. You ll note each ISA device has a separate IRQ setting, while multiple PCI devices share the same IRQ settings. This is very typical. Note also that the PCI Modem device has a question mark as an icon. This is because the device isn t configured properly, not because there s a conflict. In this example, there are no conflicts. 404 Part 4: Managing Windows Server 2003 Systems
If you are in need for chaep and reliable webhost to host your website, our recommendation is http web server services.

Managing and Troubleshooting Hardware Table 13-1. Common Device Error Codes and Descriptions Error Code Error Message Solution Code 31 This device is not working properly because Windows cannot load the drivers required for this device. The device driver might be incompatible with Windows Server 2003. Obtain a compatible driver for the device; click Reinstall Driver to start the Hardware Update Wizard. Follow the wizard as discussed in the section entitled Updating a Device Driver earlier in this chapter. Chapter 13 Code 32 A driver for this device was not required and has been disabled. A dependent service for this device has been set to Disabled. Check the event logs to determine which services should be enabled and started. Code 33 Windows cannot determine which resources are required for this device. Typically results from a bad device or bad hardware. Can also occur with legacy ISA devices; upgrade the driver and/or refer to the device documentation on how to set resources. Code 34 Windows cannot determine the settings for this device. The legacy device must be manually configured. Verify the device jumpers or BIOS settings, then configure the device resources as discussed in the section entitled Resolving Resource Conflicts. Code 35 Your computer s system firmware does not include enough information to properly configure and use this device. This error occurs on multiprocessor systems. Update the BIOS; check for a BIOS option to use Microsoft Personalization System (MPS) 1.1 or MPS 1.4. Usually, you want MPS 1.4. Code 36 This device is requesting a PCI interrupt but is configured for an ISA interrupt (or vice versa). ISA interrupts are nonsharable. If a device is in a PCI slot but the slot is configured in BIOS as reserved for ISA, the error might display. Change the BIOS settings. 403 Part 4: Managing Windows Server 2003 Systems
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.

Microsoft Windows Server 2003 Inside Out Table 13-1. Common Device Error Codes and Descriptions Error Code Error Message Solution Code 17 This device is asking for an unknown resource type. Reinstall or update the driver using a valid, signed driver. Code 18 Reinstall the drivers for this device. After an upgrade, you might need to log on as an administrator to complete the device installation. If that s not the case, click Update Driver in the Driver tab to reinstall the driver. Code 19 The Registry might be corrupted. Remove and reinstall the device. This should clear out the incorrect or conflicting Registry settings. Code 21 Windows is removing this device. The system will remove the device. The Registry might be corrupted. If the device continues to display this message, restart the computer. Code 22 This device is disabled. This device has been disabled using Device Manager. To enable it, select Use This Device (Enable) under Device Usage. Code 24 This device is not present, is not working properly, or does not have all its drivers installed. Typically results from a bad device or bad hardware. Can also occur with legacy ISA devices; upgrade the driver. Code 28 The drivers for this device are not installed. Obtain a compatible driver for the device; click Reinstall Driver to start the Hardware Update Wizard. Follow the wizard as discussed in the section entitled Updating a Device Driver earlier in this chapter. Code 29 This device is disabled Check the device documentation on how to because the firmware of the device did not give it the required resources. assign resources. You might need to enable the device in the system BIOS or upgrade the BIOS. Chapter 13 402 Part 4: Managing Windows Server 2003 Systems
If you are in need for chaep and reliable webhost to host your website, our recommendation is http web server services.

Managing and Troubleshooting Hardware Resolving Common Device Errors Each error code shown for a device includes a description as well as a suggested action you should take to try to resolve them. Table 13-1 summarizes the common error codes you ll see and describes the suggested actions you should take to resolve them. Most of the actions assume you have the device s Properties dialog box open to the General tab. Table 13-1. Common Device Error Codes and Descriptions Chapter 13 Error Code Error Message Solution Code 1 This device is not configured correctly. Obtain a compatible driver for the device, click Reinstall Driver to start the Hardware Update Wizard. Follow the wizard as discussed in the section Updating a Device Driver earlier in this chapter. Code 3 The driver for this device might be corrupted, or your system may be running low on memory or other resources. Run the Update Driver Wizard by clicking Update Driver in the Driver tab. You might see an Out of Memory message at startup because of this. Code 10 This device cannot start. Run the Update Driver Wizard by clicking Update Driver in the Driver tab. Don t try to find a driver automatically. Instead, manually install as discussed in the section entitled Installing Non Plug and Play Devices earlier in this chapter. Code 12 This device cannot find enough free resources that it can use. Resources assigned to this device conflict with another device, or the BIOS is incorrectly configured. Check the BIOS for resource conflicts as discussed in the section entitled Resolving Resource Conflicts later in this chapter. Code 14 This device cannot work properly until you restart your computer. Typically, the driver is installed correctly, but will not be started until you restart the computer. Code 16 Windows cannot identify all the resources this device uses. Check to see whether a signed driver is available for the device. If it is and you ve already installed it, you must manage the resources for the device as discussed in the section entitled Managing Installed Drivers earlier in this chapter. Part 4: Managing Windows Server 2003 Systems
If you are searching for cheap webhost for your web application, please visit MySQL5 Web Hosting services.

Microsoft Windows Server 2003 Inside Out Chapter 13 6 Repeat Steps 3 through 5 to create other profiles. Then set the hardware profile selection options. In most cases, you ll want the Windows operating system to select a profile automatically after a 3- to 5-second delay. That way if you don t select a profile, the computer starts quickly using the default profile. 7 Restart the computer, and then choose the profile you want to work with. Start Device Manager, and then access the Properties dialog boxes for each of the devices you want to enable or disable in turn. In the General tab, use the Device Usage settings as follows: Use This Device (Enable) Choose this option for any device that you want to make available for the current profile. Do Not Use This Device In The Current Hardware Profile (Disable) Choose this option for any device that should be disabled in the current profile. Do Not Use This Device In Any Hardware Profiles (Disable) Choose this option for any device that should be disabled regardless of which profile is used. 8 To configure devices for additional profiles, repeat Step 7. Troubleshooting Hardware Devices and Drivers Whenever a device is installed incorrectly or has another problem, Device Manager displays a warning icon indicating the device has a problem. If you double-click the device, an error code is displayed, as shown in the following screen: 400 Part 4: Managing Windows Server 2003 Systems
We highly recommend you visit web and email hosting services if you need stable and cheap web hosting platform for your web applications.

Managing and Troubleshooting Hardware Windows Server 2003 allows you to configure the way hardware profiles are used in several ways. The active profile (that is, the one currently being used) is listed as (Current). The default profile highlighted at startup is determined by the profile s position in the Available Hardware Profiles list. To set a profile as the default, select it, and click the up arrow until the profile is at the top of the list. You can also determine how long the system displays the hardware profile menu at startup. If you don t want the hardware profile menu to be displayed, set a wait of 0 seconds. To create new hardware profiles, you use a copy of an existing profile and then enable or disable devices as necessary. Follow these steps to create and use a new profile: 1 In Control Panel, double-click System to start the System utility. 2 Select the Hardware tab, and then click Hardware Profile. 3 In the Available Hardware Profiles list, select the profile you want to use as a template for the new profile, and then click Copy. 4 In the Copy Profile dialog box, enter a name for the profile, and then click OK. 5 Select the new profile, and then click Properties. For nonmobile servers, ensure the This Is A Portable Computer option isn t selected, as shown in Figure 13-8. For all computers, select Always Include This Profile As An Option When Windows Starts. Click OK. Chapter 13 Figure 13-8. Nonmobile servers don t have docked or undocked states, so clear This Is A Portable Computer if it is selected. 399 Part 4: Managing Windows Server 2003 Systems
In case you need affordable webhost to host your website, our recommendation is ecommerce web host services.

Microsoft Windows Server 2003 Inside Out Managing Devices through Hardware Profiles Chapter 13 Developers, engineers, and information technology (IT) testers often need a way to implement or test different device configurations. You can, of course, do this by enabling and disabling devices, but this can be tedious and time- consuming. A more practical way to implement multiple device configurations is to use hardware profiles. By using hardware profiles, you can create different device configurations and load them quickly by selecting the appropriate profile to use during startup of the operating system. Hardware profiles are most commonly used with mobile workstations and servers. On a portable computer with a Plug and Play compatible docking station, you ll have two profiles that are created and loaded automatically as needed: a docked profile for when the computer is connected to the network, and an undocked profile for when the computer is disconnected from the docking station. You could create hardware profiles for different device configurations as well. For example, you could have a standard profile that includes the standard devices for internal RAID controllers and drive arrays and a test profile that includes external fiber-channel devices. You could then test out the fiber- channel storage devices using the second profile and easily switch back to the standard device set when you are finished testing. You create and manage hardware profiles by using the System utility. In the System utility, select the Hardware tab, and then click Hardware Profiles. This opens the dialog box shown in Figure 13-7. Figure 13-7. Hardware profiles are useful for testing various device configurations. 398 Part 4: Managing Windows Server 2003 Systems
In case you need quality webspace to host and run your web applications, try our personal web hosting services.

Managing and Troubleshooting Hardware If you suspect that an updated driver is causing the system or device problems you are experiencing, you can attempt to recover the system to the previously installed device driver. Double-click the device in Device Manager to display the driver s Properties dialog box. Then in the Driver tab, click Rollback Driver. Chapter 13 Note You can roll back only if you ve updated the driver. If you haven t, a backup driver file won t be available. Instead of being able to roll back the driver, you ll see a prompt telling you that no driver files have been backed up for this device. If you re having problems with the device, start the troubleshooter by clicking Yes. Uninstalling and Reinstalling a Device Driver Windows device drivers for Plug and Play devices are loaded and unloaded dynamically. You can remove the driver for a device only when the device is plugged in. This means the proper way to remove a device from a system is first to uninstall its related device driver and then to remove the device from the system. One reason for uninstalling a device is to remove a device that is no longer used or needed. Start by uninstalling the related device driver. Double-click the device in Device Manager to display the driver s Properties dialog box. Then in the Driver tab, click Uninstall. When prompted, click OK to confirm that you want to remove the driver. Windows Server 2003 will then remove the related files and Registry settings. At this point, you can shut down the system and remove the related hardware component if you want to. However, you might first want to check to see how the computer operates without the device in case some unforeseen problem or error occurs. So, rather than removing the device, you ll want to disable it. Disabling the device prevents Windows from reinstalling the device automatically the next time you restart the system. You disable a device by right- clicking it in Device Manager and then selecting Disable. Sometimes when you are troubleshooting and trying to get a device to work properly, you might want to uninstall to unplug the device temporarily. Here, you could disable the device and then monitor the system to see whether problems previously experienced reoccur, or you could reinstall the device to see whether normal operations are restored. Uninstalling and then reinstalling the device forces Windows to go back to the device s original device and Registry settings, which can sometimes recover the device. After you ve uninstalled a device driver, one way to get Windows Server 2003 to reinstall the device is to reboot the computer. You can also try to rescan for devices using Device Manager by choosing Scan For Hardware Changes on the Action menu. Either way, the operating system should detect the uninstalled device as new hardware and then automatically reinstall the necessary device driver. If this doesn t happen, you must reinstall the device manually using the Add Hardware Wizard as discussed earlier in this chapter. Part 4: Managing Windows Server 2003 Systems
We would like to recommend you tested and proved virtual web hosting services, which you will surely find to be of great quality.

Microsoft Windows Server 2003 Inside Out Chapter 13 Next, check the driver version information for the driver you downloaded. To do this, unzip the downloaded driver files to a folder. In the folder, you should find .dll or .sys files. Right- click one of these files, and choose Properties. Then in the Properties dialog box, choose the Version tab to find the version information. To continue with the installation of downloaded drivers, check to see whether the driver download includes a Setup program. If it does, run this program so that the proper files are copied to your system. Once you do this, you can use the Hardware Update Wizard to install the driver. This wizard is started by accessing the driver s Properties dialog box through Device Manager and then clicking the Update Driver button in the Driver tab. As you ll see, the Hardware Update Wizard is essentially the same as the Add Hardware Wizard (see the following screen). Because of this, you follow the same procedures as discussed in the section entitled Setting Up New Hardware Devices earlier in this chapter. Keep in mind that in some cases you must reboot the system to activate the updated device driver. Rolling Back a Driver Occasionally, you ll find that an updated driver doesn t work as expected. It could cause problems, such as device failure or system instability. In most cases, this should occur only when you ve installed unsigned device drivers as a last resort or beta versions of new drivers that might have improved performance or some other benefit that outweighs their potential to crash the system. However, it can sometimes occur with signed device drivers even those published through Windows Update. 396 Part 4: Managing Windows Server 2003 Systems
Please visit Domain Name Hosting services for high quality webhost to host and run your jsp applications.