Input/Outut Range conflict, please help!

[NiceGuyEddie]

Hello all.
I've tried to install new Pinnacle DC1000DV Capture Board on my machine (Supermicro PIII DME ,2 x 256 SDRAM, Adaptec 39160,
Matrox Millennium G400 DH, SB Live Platinum)
After fresh installation of Win2k, i installed Pemiere 6 full version
Aa soon as i mount DC1000 in ANY available PCI slot, Windows 2000 automaticly install it as DEC 21152 PCI to PCI bridge and mark it yellow in Device Manager under System Devices
In Device Manager under General tab it will say: This device cannot find enough free resources that it can use. (Code 12)
If you want to use this device, you will need to disable one of the other devices on this system.
Click Troubleshooter to start the troubleshooter for this device.

Under Resources tab it will show this:
Input/Output Range 9000 - 9FFF used by:
Intel(r) 82840 Processor to AGP Controller

Input/Ouput Range 9000-9FFF marked red under Resources

I've tried every (I have 4 open) available PCI slots, with the same result. Installation of latest drivers does not help.

Please, guys, help me out, before i go nuts!

Thanx in advance
Eddie

[TOAD6147]

I would un-install all devices and start with the sound card and then the capture card. Be sure to set BIOS to non-PNP OS so that the BIOS will allocate resources automatically. If that doesn't solve the problem then you'' have to start plying around will manual allocation. How many legacy devices do you have. It would help if you could give an inventory of the IRQ's and how they are being used now. Device Manager > Computer > Properties.

[NiceGuyEddie]

Thank you for your input, TOAD6147.
Well, i'm running Win2000 Pro SP1 and the only PCI devices i have installed are Adaptec 39160 SCSI adapter (SLOT 5 - PCI64) and Live! Platinum (SLOT 2 - PCI32)
Everything works fine until i try to install capture card.

Here is what Win2000 system information shows me:
System Information report written at: 02/02/2001 11:23:19 AM
[IRQs]

IRQ Number Device
9 Microsoft ACPI-Compliant System
9 Intel(r) 82801AA SMBus Controller
16 Matrox Millennium G400 DualHead MAX - English
16 Intel 8255x-based PCI Ethernet Adapter (10/100)
28 Adaptec 3960D Ultra160/m PCI SCSI Card
29 Adaptec 3960D Ultra160/m PCI SCSI Card
17 Creative SB Live! Basic (WDM)
8 System CMOS/real time clock
13 Numeric data processor
12 Microsoft PS/2 Mouse
1 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
6 Standard floppy disk controller
4 Communications Port (COM1)
3 Communications Port (COM2)
14 Primary IDE Channel
15 Secondary IDE Channel

PnP is disabled in BIOS as well.
You might want to take a look at this:
System Information report written at: 02/02/2001 11:26:36 AM
[I/O]

Address Range Device Status
0x0000-0x0CF7 PCI bus OK
0x0000-0x0CF7 Direct memory access controller OK
0x0D00-0xFFFF PCI bus OK
0xD000-0xDFFF Intel(r) 82840 Processor to AGP Controller OK
0x03B0-0x03BB Intel(r) 82840 Processor to AGP Controller OK
0x03B0-0x03BB Matrox Millennium G400 DualHead MAX - English OK
0x03C0-0x03DF Intel(r) 82840 Processor to AGP Controller OK
0x03C0-0x03DF Matrox Millennium G400 DualHead MAX - English OK
0xB000-0xCFFF Intel(r) 82840 PCI Bridge OK
0xB000-0xCFFF Intel(r) 82806AA PCI Bridge OK
0xB400-0xB4FF Adaptec 3960D Ultra160/m PCI SCSI Card OK
0xB800-0xB8FF Adaptec 3960D Ultra160/m PCI SCSI Card OK
0xAF80-0xAF9F Creative SB Live! Basic (WDM) OK
0xAFF0-0xAFF7 Game Port for Creative SB Live! OK
0xAF00-0xAF3F Intel 8255x-based PCI Ethernet Adapter (10/100) OK
0x0A79-0x0A79 ISAPNP Read Data Port OK
0x0279-0x0279 ISAPNP Read Data Port OK
0x0274-0x0277 ISAPNP Read Data Port OK
0x0020-0x0021 Programmable interrupt controller OK
0x00A0-0x00A1 Programmable interrupt controller OK
0x0081-0x0083 Direct memory access controller OK
0x0087-0x0087 Direct memory access controller OK
0x0089-0x008B Direct memory access controller OK
0x008F-0x008F Direct memory access controller OK
0x00C0-0x00DF Direct memory access controller OK
0x0040-0x0043 System timer OK
0x0070-0x0071 System CMOS/real time clock OK
0x0061-0x0061 System speaker OK
0x00F0-0x00FF Numeric data processor OK
0x0060-0x0060 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard OK
0x0064-0x0064 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard OK
0x0010-0x001F Motherboard resources OK
0x0022-0x003F Motherboard resources OK
0x0044-0x005F Motherboard resources OK
0x0062-0x0063 Motherboard resources OK
0x0065-0x006F Motherboard resources OK
0x0072-0x007F Motherboard resources OK
0x0080-0x0080 Motherboard resources OK
0x0084-0x0086 Motherboard resources OK
0x0088-0x0088 Motherboard resources OK
0x008C-0x008E Motherboard resources OK
0x0090-0x009F Motherboard resources OK
0x00A2-0x00BF Motherboard resources OK
0x00E0-0x00EF Motherboard resources OK
0x04D0-0x04D1 Motherboard resources OK
0x03F0-0x03F1 Motherboard resources OK
0x0480-0x04BF Motherboard resources OK
0x0680-0x06FF Motherboard resources OK
0x0400-0x047F Motherboard resources OK
0x03F2-0x03F3 Standard floppy disk controller OK
0x03F4-0x03F5 Standard floppy disk controller OK
0x03F7-0x03F7 Standard floppy disk controller OK
0x03F8-0x03FF Communications Port (COM1) OK
0x02F8-0x02FF Communications Port (COM2) OK
0x0378-0x037F ECP Printer Port (LPT1) OK
0x0778-0x077F ECP Printer Port (LPT1) OK
0xFFA0-0xFFAF Intel(r) 82801AA Bus Master IDE Controller OK
0x01F0-0x01F7 Primary IDE Channel OK
0x03F6-0x03F6 Primary IDE Channel OK
0x0170-0x0177 Secondary IDE Channel OK
0x0376-0x0376 Secondary IDE Channel OK
0xEFA0-0xEFAF Intel(r) 82801AA SMBus Controller OK

Thanx again
Eddie

[stevenvee]

Since you are not using your com ports you might consider disabling them and using those irqs.

If that doesn't work I would start over and disable PCI bus IRQ steering, following these steps:

Click Start, point to Settings, click Control Panel, and then double-click System.


Click the Device Manager tab.


Double-click the System Devices branch.


Double-click PCI Bus, and then click the IRQ Steering tab.


Click the Use IRQ Steering check box to clear it, click OK, and then click OK again.


When you are prompted to restart your computer, click Yes.

NOTE: If you click No instead of Yes when you are prompted to restart your computer, the changes do not take affect.


NOTE: You may also have to disable PCI bus IRQ steering in your computer's basic input/output system (BIOS). For information about how to do so, contact you BIOS manufacturer.

The following settings determine which routing tables Windows uses when programming IRQ steering:


Get IRQ table using ACPI BIOS:

When this check box is selected, the ACPI BIOS IRQ routing table is the first table Windows tries to use to program IRQ steering. If a PCI device is not working properly, click this check box to clear it.


Get IRQ table using MS Specification table:

When this check box is selected, the MS Specification routing table is the second table Windows tries to use to program IRQ steering.


Get IRQ table from Protected Mode PCIBIOS 2.1 call:

When this check box is selected, the Protected Mode PCIBIOS 2.1 routing table is the third table Windows tries to use to program IRQ steering.


Get IRQ table from Real Mode PCIBIOS 2.1 call:

When this check box is selected, the Real Mode PCIBIOS 2.1 routing table is the fourth table Windows tries to use to program IRQ steering.

NOTE: By default, the "Get IRQ table from Protected Mode PCIBIOS 2.1 call" check box is not selected. You should only click this check box to place a check mark if a PCI device is not working properly.


IRQ Holder For PCI Steering may appear under IRQ Routing Status even though PCI bus IRQ steering is disabled. This can occur if the IRQ settings are being read by your computer's BIOS. For information about modifying the BIOS, contact your BIOS manufacturer.


MORE INFORMATION
The PCI local bus has become the industry-standard bus and is used in most Pentium computers. When a computer with a PCI local bus boots up, the system BIOS dynamically configures all the PCI card resource settings and requirements, because the PCI bus and PCI devices use agreed-upon mechanisms for identifying themselves and declaring their resource settings and/or requirements.

PCI devices can share the same IRQ's because the system BIOS builds a table called the PCI IRQ routing table, which is made up entries for each PCI device which is given an ISA IRQ that is mapped to a particular PCI INT number associated with the specific PCI slot which the device is installed to. These combined together to create a link value. The link value is used when communicating with the device, and while PCI devices may use the same IRQ, they actually all have individual link values.

After the system BIOS assigns resource settings and builds the PCI IRQ routing table, Windows will load up and will extract PCI and ISA Plug and Play-compliant device resource information from the system BIOS and read the information from the PCI IRQ routing table. Windows can at this time reassign the ISA IRQ's mapped to a particular PCI INT number. Windows can also dynamically reassign the IRQ's when a Plug and Play event occurs, such as docking a laptop with it's docking station.

Sometimes when reassigning IRQ's in this way, Windows may hang, reboot, or have a device fail to work when it tries to reassign the IRQ's setup by the BIOS. You can prevent Windows from dynamically allocating ISA interrupts by turning off IRQ steering. This prevents Windows from dynamically allocating interrupts, and relies on your system BIOS to do so.

OEM (Original Equipment Manufactures) may find it necessary to disable IRQ steering even on new PC's to prevent hardware resource conflicts on devices they have installed in a computer system. This doesn't prevent any loss of functionality for the devices, it simply insures the devices will remain enabled to use a specific IRQ configuration that the OEM has found to work properly when testing the system.


[This message has been edited by stevenvee (edited 02-05-2001).]