Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Resolving IRQ conflict under NT 4.0 wkstn.

Posted on 1997-06-12
4
Medium Priority
?
675 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
  • 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 400 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

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

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

This is an article on how to answer questions, earn points and become an expert.
Recently, I read that Microsoft has analysed statistics for their security intelligence report. It revealed: still, the clear majority of windows users do their daily work as administrator. An administrative account is a burden, security-wise. My ar…
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
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…

581 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