<< Previous Message <<
Date: | Tue, 4 Apr 2000 09:36:32 PST |
From: | "Steven Levine" <steve53@earthlink.net > |
Reply-To: | scoug-help@scoug.com |
To: | scoug-help@scoug.com |
Subject: | SCOUG-Help: NIC driver appears to unload itself |
=====================================================
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.
=====================================================
In <38EA1F72.637B@peterskye.com>, on 04/04/00
>I have several identical 10 Mbit Ethernet cards whose driver appears to
This normal for NIC drivers that are not Resource Manager aware. Few are.
>The driver issues its load messages during bootup and does not issue an
Do a RMVIEW /D or /D1. This will show if the driver is loaded. Most
> NE2000-Compatible NDIS 2.0.1 Network Driver, Version:2.4
>Note the IRQ 3 in the second line. I took a look inside the AN16.OS2
OK, it's a cheap NE-2000 clone. These may be the defaults. Did you
>The driver is dated July 6 1993. I purchased these cards new about three
These are reference drivers. You can often substitute another NE-2000
>Before I reinitialize the card to IRQ 3, move COM2 (currently on IRQ 3)
See above.
>-- if I'm looking at this problem incorrectly and should be trying
Yes.
>-- if I should trash these "AN16" cards and use the D-Link cards I have
Well, the performance will probably be much better.
Steven
--
=====================================================
To unsubscribe from this list, send an email message
For problems, contact the list owner at
=====================================================
Return to [ 04 |
April |
2000 ]
at 08:59 AM, Peter Skye
>load but which does not show up in RMVIEW.
>error message. My best guess is that the driver is unloading itself
>because it either can't find the card or can't determine the card's IRQ.
drivers support the /V option.
> NE2000-Compatible Adapter I/O ADDR:0300h, IRQ 3.
>device driver file and found these two lines were hard coded, i.e. this
>OS/2 driver _always_ reports PORT 300 and IRQ 3 no matter how the card is
>actually set up.
specify the correct values in PROTOCOL.INI?
>years ago.
driver.
>to another IRQ, and try again, I'd like to know:
>something else.
>on the shelf.
----------------------------------------------------------------
"Steven Levine"
www.scoug.com irc.webbnet.org #scoug (Mon 7pm PST)
----------------------------------------------------------------
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
"rollin@scoug.com".
<< Previous Message <<