Author Topic: Win2K IRQ conflicts  (Read 457 times)

Offline oboe

  • Plutonium Member
  • *******
  • Posts: 9805
Win2K IRQ conflicts
« on: January 20, 2002, 10:54:52 AM »
OK I'm getting pretty frustrated here and its time to ask for help be for I screw up my new machine.

I recently built an ASUS A7M266/Athlon 1800 based machine.  I am running Win2K.   My vid card is ASUS v8200 Geforce 3 Ti 200, my sound card is Turtle Beach Santa Cruz, NIC is a 3COM 3C905BTXNM PCI.
 
Problem is, all these devices are using IRQ 9.   I know this can't be optimal so I'm trying to change them,  but the "Change Settings" button in device manager under the Resouces tab is greyed out.   So is the "Use Automatic Configuration" check box.

I have tried forcing the PCI slots to use different IRQs in the BIOS settings; when I tried it for the slot my Santa Cruz is in, the device called "Multimedia Audio Controller" changed its IRQ from IRQ 10 to 5, but the devices called "Santa Cruz", "Santa Cruz Game Port", and "Santa Cruz WDM Interface" remained on IRQ 9.  (A related problem is that in the Device Manager, "Multimedia Audio Controller" says that no drivers are installed.  But I do get sound out of my system.

When I tried forcing an IRQ change thru the BIOS settings for the port the 3Com NIC is in, it just remained on IRQ 9.

I do log in as Administrator.

Other problems are that my new 3COM modem is apparently DOA, there are no Win2K drivers for my HP Deskjet 882C printer, and my Thrustmaster Attack throttle won't work with Win2K.
(I ordered a SunCom SFS throttle and Talon joystick and am going to try to convert these to USB with an Game Port to USB adapter - I read about this scheme on AGW).

I should mention I'm a first time PC builder.   Thanks for any help you can offer!

Offline AKDejaVu

  • Platinum Member
  • ******
  • Posts: 5049
      • http://www.dbstaines.com
Win2K IRQ conflicts
« Reply #1 on: January 20, 2002, 12:12:45 PM »
I have the same NIC with a SB Live vid card.  I have no problems.

I'd have a tendancy to say that if you do not have a problem with the configuration, do not attempt to change it.  It just looks funny, but Win2k does a good job handling it.

The only way to change it involves disabling the automatic hadware setup in your bios, then re-installing the OS.  Its not a fun one... and I seldomely have seen it actually solve someone's problem.

AKDejaVu

Offline oboe

  • Plutonium Member
  • *******
  • Posts: 9805
Win2K IRQ conflicts
« Reply #2 on: January 20, 2002, 01:46:02 PM »
I'm not sure but I think its a problem, or at least a bottleneck.

I do get 75 fps, which is probably limited by my monitor refresh rate anyway...
« Last Edit: January 20, 2002, 01:56:00 PM by oboe »

Offline Sancho

  • Silver Member
  • ****
  • Posts: 1043
      • http://www.56thfightergroup.com
Win2K IRQ conflicts
« Reply #3 on: January 20, 2002, 02:05:10 PM »
Shared IRQs aren't a problem in Win2k like they are in Me/98/95.  Win2k is designed to work that way.

Here's a couple threads that have discussed this: 1 and 2

I tried the whole reinstall windows 2000 in standard PC mode to see if my framerates in AH would improve.  There was no significant difference.  Sometimes it was better in ACPI mode, sometimes better with Standard PC, but it was always within 1 FPS difference.

Offline bloom25

  • Silver Member
  • ****
  • Posts: 1675
Win2K IRQ conflicts
« Reply #4 on: January 20, 2002, 04:14:16 PM »
That's not a problem - that's normal for Windows 2000 and XP.  As long as it works for you, leave it.  (The only way to get everything on it's own IRQ is to reinstall windows and press F5 immediately after setup starts and selecting standard PC.)

Windows 2000 should have included drivers for your HP printer, have you tried it yet?

Offline qts

  • Nickel Member
  • ***
  • Posts: 782
      • None yet
Win2K IRQ conflicts
« Reply #5 on: January 20, 2002, 04:34:48 PM »
If you have ACPI enabled, don't worry.

Offline mrsid2

  • Parolee
  • Silver Member
  • ****
  • Posts: 1081
Win2K IRQ conflicts
« Reply #6 on: January 20, 2002, 04:43:34 PM »
ACPI can be a problem with Soundblaster Live! family and with VIA 686B chipset. If you have one of those it's likely that you will experience stability problems with ACPI enabled.

If you don't have any of those, I don't see any reason to worry about it.

Offline bloom25

  • Silver Member
  • ****
  • Posts: 1675
Win2K IRQ conflicts
« Reply #7 on: January 20, 2002, 06:30:32 PM »
That soundblaster issue doesn't just affect the 686B VIA southbridge.  Recently Intel has discovered a similar issue with it's i850, i845, and i860 chipsets.  The problem is a PCI bus latency issue, and as of yet there is no magic fix.  Unless you've got an add on or built on ATA100 or RAID controller that you are using I doubt you will see the problem.

The problem is a complicated one, but basically what's happening is that the PCI bus has 133MB/s of bandwidth available.  As you approach that limit data corruption and instability can result.  The reason newer chipset are running into this issue is that things like ATA100 (or worse yet ATA133) hard drive data transfers can gobble up this bandwidth quickly.  Now when you go and put in a Soundblaster card that also requires a significant amount of bandwidth and you can come right up against that limit in a hurry.

VIA tried to resolve the issue with a patch that tried to basically vary the amount of time that each device had to access the PCI bus.  It helped, but doesn't actually cure the problem.

Intel has found similar issues once bandwidth requirements rise to 80 to 90MB/s.

Newer chipsets like nVidia's nForce and the VIA KT266a do not have this problem because they use their own special data bus between the "southbridge" and "northbridge" that means the PCI bus is free for other uses.  I realize some of you probably don't know what I mean by northbridge and southbridge, but basically those are the two main chips that make up a chipset.  The northbridge connects to the processor, memory, and AGP video card.  The southbridge handles almost all other traffic, such as PCI and ISA expansion cards, hard drive transfers, USB and PS/2 ports, printer port, and serial ports.  On all but the newest chipset designs all data transfers between these two chips and the components they connect to was handled over the PCI bus.  Newer chipsets link the PCI bus to the southbridge only and then link the north and south bridges by a special high performance link.  Some of these are called VIA Link and Hypertransport.

Later this year there will be major changes in this area with a new harddrive connection method called Serial ATA.  We may also see the end of the "old" PCI bus and it's replacement by 1 of several competing standards.

Here's some more info on the problem: http://www.theinquirer.net/17010203.htm
http://www.viahardware.com/686bfaq.shtm