Sometimes it is possible that a resource problem is not showing up in the conflicting resource list or as a yellow exclamation point in the Device Manager. If you have any doubt about the configuration of your device (or just want to double-check), you can view all of the devices and their assigned resources by highlighting “Computer” at the top of the Device Manager list and clicking the Properties button. This will allow you to view a list of assigned IRQ numbers on the left, and the associated devices on the right. If a number does not show up in this list, it means that it is available for use. Look also for IRQs that are shared by more than one device. While the Delta 66 may share an IRQ with some devices, not all devices are capable of sharing IRQs. An entry that reads “IRQ Holder for PCI Steering” along with an installed PCI device (such as the Delta 66) is normal. If you see another device showing up on the same IRQ as the Delta 66 (such as a video card, SCSI adapter, or USB Host Controller), then it is possible that this is the source of the conflict. Typically, if you move one of the conflicting cards to another PCI slot, an IRQ conflict will disappear.
Address conflicts are rare amongst PCI devices, but if there is no obvious IRQ conflict, why not check for I/O Address conflicts while in the Device Manager? You may view the list of assigned I/O addresses by selecting the “Input/output (I/O)” radio button below the “Interrupt Request (IRQ)” radio button at the top of the Device Manager page. I/O addresses are displayed as
If scanning all the resource lists in the Device Manager does not provide an answer or clue to the resource conflict, you might want to exit Windows and do a final inspection of your computer’s BIOS setup. Some newer BIOS’s (see your computer manual) allow the reservation of an IRQ for each PCI slot on the motherboard. This may be very handy in resolving IRQ assignments for PCI devices.
Also, sometimes a BIOS is configured to direct a particular IRQ to an ISA legacy device
41
