Solved

Resolving IRQ conflict under NT 4.0 wkstn.

Posted on 1997-06-12
4
623 Views
Last Modified: 2013-12-14
I have a Zenith GT-166 running NT Workstation 4.0.  I have an Intel EtherExpress 82557 PCI-Based 10/100 ethernet card which is at IRQ 11, which works fine by itself.  However, when I add an Colorado System SC 50 SCSI card (really an Adaptec 15xx (AIC 6x60)), on which I've set the jumper to IRQ 10, NT loads the sparrow.sys driver at IRQ 11 instead of at IRQ 10 (there's also an I/O conflict at 140-15F).  How can I get the sparrow.sys driver to recognize that there's already a device at IRQ 11?  I've noticed that running the NT diagnostics program and looking at resources/IRQs only shows the ISA resources and IRQ 11 appears free, so somehow I need to make the system aware that IRQ 11 is already taken.  Thanks!
0
Comment
Question by:pjwagner
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 2

Expert Comment

by:czamudio
ID: 1766248
Try checking the automatic settings for PCI cards in your bios.
0
 

Author Comment

by:pjwagner
ID: 1766249
The comment from czamudio above led to a solution!  In the
BIOS settings there's a Plug and Play section, and in there
it listed IRQs considered open.  I manually changed IRQ 11
from "Open" to "Used by an ISA Device", and when I rebooted
NT moved my ethernet card to IRQ 9 and the SCSI card is now
happy at IRQ 11.  Thanks!  (note to czamudio - please submit
this as the answer for credit :-)
0
 

Accepted Solution

by:
jacobsr earned 100 total points
ID: 1766250
To over ride the hard coded IRQ 11 in SPARROW.SYS:

1. Back up your registry

2. Unless you have a lot of spare time and all your NT 4 tools, back it up again.

3. Get Q102991 from the Knowledge Base; even though it refers to NT 3.1, the principle seems to be the same.

4. Using REGEDIT add "Parameters" as a subkey under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Sparrow

5. Add "Device0" as a subkey under "Parameters," just established.  If the SCSI card is not the only SCSI card in the system, you may have to change the "0" to "1" or whatever.

6. Add as a string value under "Device0" "DriverParameter"

7. Set the value of DriverParameter to "IRQ=12" (no quotes needed; REGEDIT will add them automatically).  My card's IRQ was 12; yours may differ and you must set the IRQ to the actual IRQ.

8. Reboot & check the event log and NT diagnostics to make sure that the new IRQ is in place.  You shouldn't see any more Error 13 entries in the log, and the "Resources" tab in NT diagnostics should show the correct IRQ for the card.

Best wishes to all.

Robert Jacobs
Xjacobsr@cwu.edu  (remove the "X" to correspond)

NB -- The Sparrow driver _may_ operate by polling rather than by interrupt after this fix.  Performance will be better with interrupts.  If you _can_ put it on IRQ 11, you may be somewhat better off.  -- RCJ
0
 

Author Comment

by:pjwagner
ID: 1766251
This worked great - my previous solution of changing the
Plug and Play settings in the BIOS to allow configuration
of interrupts through Setup resolved my IRQ conflict but
left me with other problems (such as LPT1: not being
accessible).  The above suggestion seems to allow all cards
and devices to coexist.  Thanks much for the response!
- Paul
0

Featured Post

Why Off-Site Backups Are The Only Way To Go

You are probably backing up your data—but how and where? Ransomware is on the rise and there are variants that specifically target backups. Read on to discover why off-site is the way to go.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A project that enables an administrator to perform actions within a user session context not just at the time of login but any time later on day(s) or week(s) later.
This article summaries thoughts and ideas from two years of sustained use. It provides good reasoning to make the jump to Windows 10.
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question