PCI controller cards have no control over what resources (or IRQ / Interrupt request) they will be using. Under the PCI specification, the resources will be defined by the computer system's CMOS and possibly by the systems PnP (Plug-N-Play) support and PnP operating system (assuming that the operating system supports PnP). Resources are assigned to the PCI slot and then passed along to the card plugged into that slot.

Most PCI cards, have no jumpers on them to control resources. Although the IRQ being assigned may be displayed within the Operating System or the BIOS of the controller, this is reporting the resource that has been assigned to it only and cannot be changed within the PCI card.

Here are some suggestions and basic requirements to check for when experiencing a conflict with other I/O cards.

On the computer system:

If at all possible, try to define an unique IRQ for the PCI card.

- This is a motherboard CMOS and PnP (Plug-N-Play) function or setup and is not adjustable on the PCI card. If PnP (Plug-N-Play) is not working, then try to disable the PnP function of the computer BIOS (if the motherboard allows this option).

Note: Some computers may allow the sharing of IRQs. Double check and make sure the device which is sharing with your PCI card is also capable of sharing IRQs. (It is recommended, if possible to assign a unique IRQ to the SCSI card.)

The IRQ defined must be set to Level Triggering.
- There are two type of triggered IRQs, "Edge" or "Level", which is usually an option within the systems CMOS/BIOS but not all systems will have this option.

The PCI card must be in a Bus Mastering PCI Slot. Double check the PCI specifications of the motherboard or the computer vendor, to see if the PCI slot being used supports Bus Mastering. Some systems may use the first or the first two PCI slots on the motherboard as the only BUS mastering PCI slots. Also to check with the computer / motherboard manufacturer to verify the PCI slot is 2.1 compliant.

- In most systems simply moving the controller to a different PCI slot, may also change the resources of the controller, thus resolving resource issues.

- Another simple test is to swap the PCI card, from the PCI slot it is in, with another PCI card in the system.

Side Note: If there is an AGP Video card in the system, these can sometimes cause memory conflicts and by simply by moving the PCI card away from the AGP card, will help.

If all of these options have been verified and tried, here are some additional options:

It has been observed in some systems where the order of which the controller cards, being installed on the system makes a difference. The actual sequences of which card is installed first, then second, then third.

Another possibility, is the problem might still be within the PnP BIOS of the computer and may require a motherboard firmware or BIOS upgrade. If the firmware or BIOS is already the latest revision and this does not resolve the issue, then you may need to call the computer manufacturer directly for additional options, if any.

Adaptec unfortunately does not have control over how the PnP (Plug-n-Play) function will define resource on your I/O cards or your PCI cards.

Additional information:
If an ISA or any legacy controller that uses a specific IRQ inside the system:

Note: This may not apply to new computers since most current systems on the market, no longer allow the use legacy or ISA legacy products.

Some computer systems, but not all, that have a PnP (Plug-N-Play) option setup inside the system BIOS and will require the setting of a particular IRQ for "ISA / ISA Legacy" or "PCI / Plug-N-Play" use only. Assuming, as an example, the legacy device is using IRQ-11 on a particular ISA or legacy card, then within system BIOS, set the "Plug-N-Play" option to define IRQ-11 for ISA or ISA/Legacy use only. This is sometimes required so that the PnP card (the SCSI controller) can not use the same IRQ. This is a function within the CMOS of the motherboard and it may require calling the motherboard manufacturer.