|
Device Managaer Conflicts Symbols |
If there is a problem with a device, it is listed in the hardware tree
list under Computer.
The problem device has a symbol indicating the type of problem:
A black exclamation point (!) on a yellow field indicates the device
is in a problem state.
A device in a problem state can be functioning. A problem code explaining
the problem is displayed for the device.
A red "X" indicates a disabled device. A disabled device is a device that is physically present in the system, consuming resources, but does not have a protected-mode driver loaded.
A blue "i" on a white field on a device resource in Computer properties indicates that Use Automatic Settings is not selected for the device and that the was manually selected. It does not indicate a problem or disabled state.
NOTE: Some sound cards and video adapters do not report all the resources
they are using to Windows 95. This can cause Device Manager to show only
one device in conflict, or no conflicts at all. This can be verified by
disabling the sound card, or using the standard VGA video driver too see
if the conflict is resolved. (This is a known problem with S3 video cards
and 16-bit Sound Blaster sound cards, or those sound cards using Sound
Blaster emulation for Sound Blaster compatibility.)
When you select a specific device in Device Manager, then click the
Properties button, you see a property sheet. The property sheet has a General
tab.
NOTE: Some devices may have other tabs besides the General tab.
Not all property sheets have the same tabs; some devices may have a
Resource tab, Driver tab, and Settings tab, or some combination of these.
At the top of the property sheet, there is a description of the device. When you click the Resource tab, the window in the middle of the tab indicates which resource types are available for the selected device.
The scroll box at the bottom of the contains a Conflicting Device list.
This list indicates a conflict with an error code.
Note the Use Automatic Settings check box. If Windows 95 successfully
detects a device, this check box is selected and the device should function
correctly.
However, if the resource settings are based on Basic Configuration
(where is any number from 0 to9), it may be necessary to change the configuration
by selecting a different basic configuration from the list. If the particular
configuration you want for the device is not listed as a basic configuration,
it may be possible to click the Change Settings button to manually adjust
the resource values.
For example, to edit the Input/Output Range setting, use these steps:
1. Click the Use Automatic Settings check box to clear it.
2. Click the Change Setting button.
3. Click the appropriate I/O range for the device.
Please see:
http://www.microsoft.com/support/tshoot/w95startup.htm
This article lists error codes that may be reported by Device Manager,
and describes how to resolve the errors. To view error codes, follow these
steps:
1. In Control Panel, double-click System.
2.Click the Device Manager tab.
3.Double-click a device type (for example, double-click Mouse) to see
the devices in that category.
4.Double-click a device to view its properties. If an error code has
been generated, the code appears in the Device Status box on the General
tab.
MORE INFORMATION
Troubleshooting Device Conflicts with Device Manager. See:
http://support.microsoft.com/support/kb/articles/q133/2/40.asp
Code 1 This code means the system has not had a chance to configure the device. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 2 This code means the device loader (DevLoader) failed to load a device. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 3 This code means the system has run out of memory. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 4 This code means the .inf file for this device is incorrect. For example, the .inf file specifies a field that should be text, but is binary instead. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, please contact the hardware's manufacturer for an updated .inf file.
Code 5 This code means there was a device failure due to the lack of an arbitrator. If a device requests a resource type for which there is no arbitrator, you receive this error code. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 6 This code means there is a conflict between this device and another device. To resolve this error code, see the "Troubleshooting Conflicting Hardware" topic in Windows 95 Help, or see the following article in the Microsoft Knowledge Base:
Code 7 This code means that no configuration can be performed on the device. If the device works correctly, you do need not to perform any steps to correct the code. If the device does not work correctly, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code and the device does not function properly, check with the hardware's manufacturer or the Microsoft Software Library for an updated driver.
Code 8 This code means the device loader (DevLoader) for a device could not be found. For example, the .inf file for the device may refer to a missing or invalid file. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer about an updated .inf file.
Code 9 This code means that the information in the registry for this device is invalid. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, contact the hardware's manufacturer for the proper registry settings.
Code 10 This code means that the device failed to start (for example, it is missing or is not working properly). To resolve this error code, make sure the device is attached to the computer correctly. For example, make sure all cables are plugged in fully and that all adapter cards are plugged into their slots fully.
Code 11 This code means that the device failed. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 12 This code means one of the resource arbitrators failed. This can occur if the device is software configurable and it does not currently have a resource, if the system is out of resources (for example, all the interrupts are in use), or if the device requests a resource and that resource is currently in use by another device that will not release the resource. To resolve this error code, see the "Troubleshooting Conflicting Hardware" topic in Windows 95 Help, or see the following article in the Microsoft Knowledge Base:
Code 13 This code means the device failed due to a problem in the device driver. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 14 This code means the device has a problem that may be resolved by restarting your computer. To resolve this error code, shut down Windows 95, turn off your computer, and then turn it back on.
Code 15 This code means the device's resources are conflicting with another device's resources. To resolve this error code, see the "Troubleshooting Conflicting Hardware" topic in Windows 95 Help, or see the following article in the Microsoft Knowledge Base:
Code 16 This code means the device was not fully detected. When a device is not fully detected, all of its resources may not be recorded. To resolve this error code, click the Resources tab in the device's properties to manually enter the settings.
Code 17 This code means the device is a multiple-function device and the .inf file for the device is providing invalid information on how to split the device's resources to the child devices. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, please contact the hardware's manufacturer about an updated .inf file.
Code 18 This code means that an error has occurred and the device needs to be reinstalled. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 19 This code means the registry returned an unknown result. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 20 This code means VxD Loader (Vxdldr) returned an unknown result. For example, there could a version mismatch between the device driver and the operating system. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 21 This code means the device has a problem that may be resolved by restarting your computer. To resolve this error code, shut down Windows 95, turn off your computer, and then turn it back on.
Code 22 This code means the device is disabled.
To resolve this error code, enable the device. To do so, follow these steps:
1.In Control Panel, double-click System.
2.Click the Device Manager tab.
3.Double-click the category for the device you want to enable, and then double-click the device.
4.In the Device Usage box, click the check box for the configuration in which you want to enable the device. For example, click the Original Configuration (Current) check box to select it.
5.Click OK, and then click Close.
6.Shut down and restart your computer.
Code 23 This code means the device loader delayed the start of a device and then failed to inform Windows 95 when it was ready to start the device. To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 24 This code means that the device was not found (for example, it is missing or is not working properly). To resolve this error code, make sure the device is attached to your computer correctly. For example, make sure all cables are plugged in fully and that all adapter cards are plugged into their slots fully.
Code 25 This code occurs only during the first reboot in Windows 95 Setup and is not visible. No resolution is necessary.
Code 26 This code means a device failed to load or that there may be a problem in the device driver (for example, the file may be damaged).
To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel. If you continue to receive this error code, check with the hardware's manufacturer or the Microsoft Software Library for an updated driver.
Code 27 This code means the portion of the registry describing possible resources for a device does not contain valid entries. For example, the device is marked as configurable, but the configuration information in the .inf file is set to hardwired.
To resolve this error code, use Device Manager to remove the device and then run the Add New Hardware tool in Control Panel.
Code 28 This code means the device was not installed completely.
To resolve this error code, click the Driver tab in the device's properties and then click Change Driver to update the driver.
Code 29 This code means the device has been disabled because the device does not work properly and cannot be made to work properly with Windows 95.
You may be able to resolve this error code by enabling or disabling the device in the computer's CMOS settings. Windows 95 cannot override this setting. Please contact the computer's manufacturer for assistance with using the computer's CMOS setup program.
Code 30 This code means that an IRQ cannot be shared. This may occur when a PCI/EISA SCSI controller is sharing an IRQ that is also in use by a real- mode device driver that Windows 95 does not take over.
To resolve this error code, remove the real-mode driver that is using the same IRQ as this device. The real-mode driver may be loading in the Config.sys or Autoexec.bat file. MAKE A LIST AND PRINT IT TWICE
A printout of your system settings is a good reference to keep handy
for
hardware troubleshooting. Right-mouse click on My computer, select Properties,
and click on the Device Manager tab.
Click on Print, choose the type of report you'd like to print, and
click on OK.
"System summary" prints a report organized by resource type-- IRQ,
I/O port, memory, and DMA channel--listing the hardware that uses each
resource. (Double-click on Computer back on the Device Manager tab to view
this information on-screen.) "Selected
class or device" lists the resources and any device drivers used by
the selected hardware. Of course, you'll need to select the hardware before
clicking on Print. And the third option, "All devices and system summary,"
prints a system summary and details for every piece of hardware on your
system.
If a hard ware such as a mouse, modem or CD-ROM didn't get detected
automatically and you know that CMOS settings and the hardware is OK then
you could have IRQ or I/O port conflict.
The best way to find out is go to the Control Panel\System icon\Device
manager tab and click print, don't select to print the whole report because
you will end up with 40 pages.
A red "X" indicates a disabled device. A disabled device is a device that is physically present in the system, consuming resources, but does not have a protected-mode driver loaded.
There's a number of reasons for this happening.
Floppy disk drive controller failure
Floppy disk drive failure
The floppy disk drive controller may not be supported in protected mode.
There are drivers loading in the CONFIG.SYS or AUTOEXEC.BAT file that may be necessary for protected-mode access.
There are drivers loading in the CONFIG.SYS or AUTOEXEC.BAT file that may be causing conflicts in Windows 95 and need to be disabled.
First: Are any conflicts shown when you go into device manager. Click on My Computer, then click on Control Panel, then click on the System Icon. Click on the Device Manager Icon and scroll down to the floppy disk controller and click on the + sign to expand it. Click on the Floppy Disk Controller and then click properties. Click the Resources Tab and check the conflicting devices tab. If there are any conflicts, please note what they are and post them here.
If there are no conflicts, then go on......
1. Check both your Config.sys and Autoexec.bat files to make sure that no devices are being loaded other than maybe Himem.sys, Emm386 and maybe your mouse. Use the REM statement before any other line loading a device, save the file and reboot the system.
If this does not cure the problem, go on.......
1. Use the right mouse button to click My Computer, then click Properties on the menu that appears.
2. Click the Device Manager tab.
3. Double-click Floppy Disk Controllers.
4. Click the floppy disk controller, and then click Remove to remove the controller.
5. Click OK.
6. In Control Panel, double-click Add New Hardware.
7. Click Next, and then click Yes to allow Windows 95 to detect the hardware in your computer.
8. When the Add New Hardware Wizard is finished, restart the computer and try to access the floppy disk drive again.
If nothing has changed after both of these procedures, in all probability the floppy disk controller is either not supported by a Windows 95 Protected Mode Driver (unlikely) or the controller or the drive has failed.
http://support.microsoft.com/support/kb/articles/q131/6/90.asp
If you are having problems with a floppy disk drive (such as receiving the error message "Error reading drive <X>:"), try the troubleshooting tips in the following sections.
Safe Mode
Start Windows 95 in Safe mode by restarting your computer and pressing the F5 key when you see the "Starting Windows 95" message. Try to access the floppy disk drive after Windows 95 starts. If you can access the floppy disk drive, follow these steps:
1.Use the right mouse button to click My Computer, then click Properties on the menu that appears.
2.Click the Device Manager tab.
3.Double-click Floppy Disk Controllers.
4.Click the floppy disk controller for the drive you are having problems with, then click Properties.
5.Click the Original Configuration (Current) check box to clear it. This disables the Windows 95 protected-mode driver for the floppy disk drive controller.
6.Click OK.
7.Restart Windows 95 normally.
If you can access the floppy disk drive successfully after following the above steps, the following conditions may be true:
The floppy disk drive controller may not be supported in protected mode. There are drivers loading in the CONFIG.SYS or AUTOEXEC.BAT file that may be necessary for protected-mode access. There are drivers loading in the CONFIG.SYS or AUTOEXEC.BAT file that may be causing conflicts in Windows 95 and need to be disabled.
If you still cannot access the floppy disk drive after following steps 1-7, follow these steps:
1.Use the right mouse button to click My Computer, then click Properties on the menu that appears.
2.Click the Device Manager tab.
3.Double-click Floppy Disk Controllers.
4.Click the floppy disk controller, and then click Remove to remove the controller.
5.Click OK.
6.In Control Panel, double-click Add New Hardware.
7.Click Next, and then click Yes to allow Windows 95 to detect the hardware in your computer.
8.When the Add New Hardware Wizard is finished, restart the computer and try to access the floppy disk drive again.
Redetecting the floppy disk controller should resolve any addressing problems with the controller by detecting the correct address range. If the floppy disk controller is not detected correctly, there may be a problem with the hard disk controller. If the floppy disk controller is redetected but you still cannot access the floppy disk drive, there may be a problem with the floppy disk.
Damaged Disks
Use the following steps to check for a damaged disk:
1.Use a disk utility (such as ScanDisk) to test the disk for damage.
NOTE: Do not use a non-Windows 95-aware disk utility on DMF disks. Non-Windows 95-aware disk utilities can damage DMF disks. The Windows 95 ScanDisk tool recognizes and does not damage DMF disks.
Before you run a disk utility, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q120442
TITLE : Using Hard Disk Utilities with Windows 95
2.Type the following command at an MS-DOS command prompt
copy <drive>\*.* nul
where <drive> is the floppy disk drive you are having problems with. For example, if you are having problems with drive A, insert a disk you are having problems with in drive A and type the following command:
copy a:\*.* nul
This command copies the files on the disk to a null device. If there is a problem copying the files, error messages appear on the screen.
CMOS Settings
Consult your computer's documentation or manufacturer to make sure that your computer's CMOS settings are correct.
Irwin Tape Backup
Windows 95 Setup removes the following statement from the [386Enh] section of the SYSTEM.INI file:
device=<path>\VIRWT.386
If you re-install the Irwin Tape Backup software after you install Windows 95, this statement is placed in the SYSTEM.INI file again and can cause conflicts with floppy disk access in Windows 95.
Device Conflicts
Device conflicts as reported by Device Manager can cause problems reading from and writing to floppy disks. You can resolve this problem by changing or removing the resources from Device Manager that are causing the conflict. These are typically conflicts with hard drive controller cards, video cards, or COM ports.
A red "X" indicates a disabled device. A disabled device is a device that is physically present in the system, consuming resources, but does not have a protected-mode driver loaded.
1. Reboot the system in the Bios setup. Make sure that your serial ports are set to auto (if possible) or enabled if older Bios, and that PS/2 support is enabled. You may have more than one area where this may need to be done, including some Bios's that have an entry something like PS/2 Mouse Support Y/N. Make sure you save the setup.
2. As the system boots through and as the dialogue comes up, "Starting
Windows 95",
touch the F8 key and bot into safe mode. Check to see if your mouse
and keyboard function, if they do, then go into device manager, scroll
down to the mouse entry, click on the "+" sign to expand it, highlight
the mouse entry and then click remove.
3. Reboot the system. It should now find your PS/2 mouse and everything
should
function.
On some MotherBoards, Windows 95 Finds a PS/2 mouse port with no PS/2 mouse attached.
The keyboard controller used on all of the Advanced line of products
is capable of
supporting a PS/2 style mouse although not all of the Advanced line
of products have a connector for a PS/2 style mouse on the baseboard. Windows
95 recognizes that the controller is capable of supporting the PS/2 mouse
and allocates resources to the mouse port (I/O port addresses and interrupt
12 [IRQ12] even if the PS/2 mouse connector does not exist or if the connector
exists and no PS/2 mouse is attached.
This problem can occur in BIOS versions 1.00.03.BS0, 1.00.04.BR0, 1.00.03.CB0,
1.00.04.BT0, and all previous versions.
Work Around
Windows 95 can be instructed to release the I/O port addresses and IRQ12 by using the following steps:
1. Click on the "Start" button (located in the lower left-hand corner
of the screen)
2. Move the arrow up to highlight "Settings"
3. Move the arrow to the right and highlight "Control Panel" click
the mouse button
4. Double click on the "System" icon
5. Click on the "Device Manager" tab
6. Highlight "PS/2 Compatible Mouse Port" under "Mouse" in the device
tree (If "PS/2 Compatible Mouse Port" is not seen, expand the tree a level
by clicking on the '+' sign or by double clicking on "Mouse")
7. Click on the "Properties" button
8. Uncheck the "Original Configuration (Current)" click "OK" shutdown
and reboot the system.
The "PS/2 Compatible Mouse Port" will now have a red X through it which means the device is not being used.
NOTE: If you use the "Remove" option in the "Device Manager", on the next reboot, the PS/2 controller will again be auto-detected and installed!
1. Restart your system and boot into the Bios/Cmos setup. Click into the standard setup area and check the floppy drive information for your installed drive, eg: if you have installed a 1.44 (3 1/2") floppy drive and that is your only floppy, make sure that is the designation for your drive "A" and then save the Bios/Cmos setup.
2. Next, as your computer begins to boot into Windows 95, touch the F8 key and boot into Safe Mode.
3. Once in safe mode, click Start, Settings, Control Panel and click the System Icon and then click the Device Manager tab. Scroll down to Disk Drives and click on the "+" sign to expand it and then highlight the floppy drive and then click the "Remove" button. If there are more than one floppy drives shown, remove them all.
4. Scroll down further to the Floppy Disk Controller and click on the "+" to expand it. Highlight the controller entry and then click on the Remove Button and remove it.
5. Restart your system. Windows will now find your floppy disk controller during the boot process and reload the protected mode driver. It will do likewise with the floppy drive.
NOTE: If you have installed one of the newer DMF high density floppy drives or an LS120 floppy instead of the typical 3.5" or 5 1/4" floppy drives, the above may not help you.
Always back up your registry 1st. 1st HKEY_LOCAL_MACHINE\SYSTEM\CURRENT CONTROLSET\SERVICE\VXD\IOS There make you "String Value Key" NOIDE=00 or NOIDE=01 You'll have to experiment with the value
To cause Windows 95 to attempt to reinitialize the protected-mode IDE
driver, remove the
NOIDE entry from the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CURRENT CONTROLSET\SERVICES\VXD\IOS
After you update the registry, restart Windows 95. Windows 95 will then attempt to initialize the protected-mode driver for the controller. If no problems are encountered, the file system and virtual memory will operate in 32-bit mode, and Device Manager will not display an exclamation point in a yellow circle for the IDE channels.
If the protected-mode driver is not initialized properly, an error message will be displayed and the NOIDE registry entry will be re-created. Windows 95 will use the MS-DOS compatibility mode file system the next time you start the computer.
2nd: Search your registry for "BAD_IDE" [no qoutes] EXAMPLE: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\hdc\0000] "InfSection"="BAD_IDE"
Delete any value that ="BAD_IDE"
1. Win95 verifies if your BIOS is P&P or not.
2. Determines which hardware profile you are using. (hardware detection
is done here!)
3. Load any real mode drivers. (Old Config.sys/Autoexec.bat stuff)
4. Initialize static VxDs (including dynamic VxD support, the Virtual
Machine Manager,
and the real mode loader.) (VMM32.VXD!)
5. Loading Protected Mode OS. (This includes Protected Mode VxDs)
6. Loading Kernal32.dll, Krnl386.exe, GDI.exe, GDI32.EXE, User.EXE,
User32.EXE,
fonts, checking the Win.ini values, shell and destop.
VxD is a virtual device driver for a hardware device that is in the Windows/System. These are for any cards and system resources built into the MoBo, and are machine specific. Because of the way the VMM32.VXD is designed, it is dynamic and changes every time your hardware changes. The files that go into this file are contained in the system\vmm32 subdirectory under your windows sub.
To find out when/where the slowdown/stop occurs, F8 at the Starting Windows 95 message and do a bootlog startup. The bootlog.txt is in the root of the startup drive. (Usually the C:\) You can hit the reset button when you get to the slowdown and do a command prompt start from there. Then look at the bootlog to see where it hangs.
STEP 1.
If the device driver (referenced in the error) has a .vxd extension,
it is a driver designed for use with Windows 95 and is referenced in
the registry.
Locate the value that references the missing device driver in the registry,
and then delete that registry value.
NOTE: ALWAYS BACKUP YOUR REGISTRY FIRST
WRPV3.ZIP is the Best and easiest Backup/Restore I've Seen.
Go To: http://www.webdev.net/orca/system.html Search WRP
STEP 2.
Disable the line referring to this device driver in the System.ini
file.
To do this, follow these steps:
1.Edit the System.ini file using any text editor (such as Edit.com).
2.Locate the line that references the file in the error message.
3.Place a semicolon at the beginning of the line as in the example
below:
4.Save and then close the System.ini file.
5.Restart the computer.
STEP 3.
Are the StaticVxD values in the registry incorrect?
If a specific device driver is not named in the error message, one of
the StaticVxD values in the registry is probably blank or contains only
spaces. The StaticVxD values are located in the registry keys below the
following key:
HKEY_LOCAL_MACHINE\System\Current ControlSet\Services\VxD
Use Registry Editor to locate and delete any StaticVxD value in the
registry that contains invalid data, is blank, or contains only spaces.
STEP 4.
Have you recently removed a program from your computer?
If you have recently removed a program or componet, reinstall the program
or component, then run the uninstall tool if one is available. If no uninstall
tool is available for the program or component, contact the manufacturer
to obtain instructions on uninstalling.
http://support.microsoft.com/support/kb/articles/q138/8/99.asp
The Ios.log file is created by the I/O Supervisor (IOS) as it attempts
to determine whether or not it can safely install 32-bit drivers. Windows
95 creates an IOS.LOG file in the Windows directory if any drives are using
MS-DOS Compatibility mode. The Windows 95 protected-mode IDE disk driver
(Esdi_506.pdr) is used to provide 32-bit disk access
MS-DOS Compatibility Mode Problems with PCI-IDE Controllers http://support.microsoft.com/support/kb/articles/q151/9/11.asp The protected-mode driver for the hard disk controller was not properly initialized when you started Windows 95 previously. When this occurs, a NOIDE entry is placed in the registry, preventing Windows 95 from making future attempts to initialize the protected-mode driver.
Do a setup /P f. This will FORCE Win95 to redetect the hardware and set up the system right. Just be sure to turn off any Virus detection in the BIOS or auto in the configs.
http://support.microsoft.com/support/kb/articles/Q130/1/79.asp
Update esdi_506.pdr - the protected mode driver for IDE, EIDE
http://www.cyf-kr.edu.pl/ftp/softlib/full.html
Look for REMIDEUP.EXE Updated ESDI_506.PDR For Windows 95
This is a very large File Base.
Now that you’ve invested in a SCSI controller, it's time to plug in the SCSI peripherals that will really make your PC zoom. Depending on the type of SCSI controller you have, you can add up to seven peripherals. Here are a few installation tips to help you install your SCSI devices right the first time.
Let’s See Some SCSI ID
The SCSI card and each peripheral you connect to it must have a unique ID number ranging from 0 to 7. External peripherals' IDs are usually set with a switch located at the rear of the case; internal peripherals' IDs are set with jumpers. ID numbers don't have to be sequential, as long as the card and each peripheral has a different number.
Record SCSI ID Number Settings
To save time when adding a new SCSI device to your system, keep a list handy of your current SCSI devices and their SCSI ID settings. You can pick an unused ID for a new device more quickly if you know which IDs are already taken.
The Lower the SCSI ID Number, the Better
One of the first devices you might want to install is a SCSI hard drive. To take advantage of its faster performance, set the drive to a low SCSI ID number (0, 1, or 2). Lower ID devices will achieve slightly faster access times over the SCSI bus. And if this drive is your boot drive, the SCSI adapter may require it to be set at 0.
Delayed Start
If you have several SCSI devices attached to the same SCSI controller, you may want to set them to Delayed Start via jumper settings on the devices (read the documentation that comes with each component). Starting all the SCSI devices at the same time when you boot your PC could drain power and cause errors. With Delayed Start, the SCSI controller sends a start signal to each device sequentially.
Termination
The most common SCSI mistake is setting the termination jumpers incorrectly. Each end of a SCSI chain of devices (both internal and external chains) needs to be terminated. If your internal SCSI device resides at the end of the chain, you must switch the termination jumper on or it won't function properly. Read the drive's documentation on how to set this jumper.
1. Determine which chipset you have on the motherboard (eg: HX, TX etc) and then download the appropriate Intel PCI Bus Mastering drivers that you need from here:
2. Then expand them and install them. Once you have installed them, go into device manager and expand the hard disk controller area and highlight and remove all entries shown.
3. Restart the system. Windows should recognize the bus correctly, and
if the cd rom drive is Atapi, it should install protected mode
drivers for it as well.
The reason that your modem is going to COM3 is because COM2 is active
on the motherboard, here is
what you should do in details:
1. Start > Settings > Control Panel
2. Click on Device Manager
3. Expand the modem section
4. Remove the modem
5. Restart your system
6. When you see in DOS the HIT DEL TO ENTER SETUP, do that:
7. In the BIOS I want you to go to where it says COM2 and its address, and DISABLE it, put it to NONE.
8. Now let the system start
9. In windows let it detect your modem, BUT use your modem installation