<< Previous Message << >> Next Message >>
Date: | Sat, 29 Jul 2000 09:49:00 PDT |
From: | Peter Skye <pskye@peterskye.com > |
Reply-To: | scoug-help@scoug.com |
To: | scoug-help@scoug.com |
Subject: | SCOUG-Help: D-Link PnP Challenges Tekram SCSI To Steel Cage DSL Match |
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Steven Levine wrote:
>
> >But I want to _lock_ the NIC IRQ so it won't "shift
> >around" if there's any future hardware changes.
> >Removing IRQ 12 from the "available" list doesn't do that.
>
> Shifting IRQ's on PCI devices are not the problem.
> Undected use of IRQ's by ISA devices is. Solve
> that problem and shift IRQ's don't matter.
>
> >The NIC IRQ is included in the PROTOCOL.INI file, yes?
>
> You can't specify it for the NIC. It's not an option.
Ummm, in the PROTOCOL.INI file for _my_ UMC NIC there's an "interrupt ="
line. It was installed as IRQ 3 (even though I'd initialized the card
to IRQ 10), and I had to manually change the PROTOCOL.INI entry to IRQ
10. (There's also an "iobase =" line.) These values are picked up by
the UMC NIC driver when the driver loads (I tested to verify this).
I don't know what the D-Link will do, but I'll find out a little later
this morning. Perhaps some NICs do this and others don't.
- Peter
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
Return to [ 29 | July | 2000 ]