• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

NIC error at boot, ok after Device Manager refresh

jayR

Senior member
This is a grey beard challange. A big thanks in advance for pointers. This will be a test of your memory(flesh & blood. F&B?)

I have a ISA nic (don't laugh at the antiquity of this stuff. It serves my purposes, or will if I can get it to work!) that says Novell, Inc. on the front and Microdyne on the back. The chip is National Semiconductor 8390. I believe this is supposed to be a NE2000 compatible card. Probably not pnp.

I am trying to get it to work on an Atrend 5010M mobo w/winme. STOP LAUGHING!!!

I have the jumpers set for IRQ 5 and I/O 300-31F. No conflicts are shown in Device manager.

I have DISABLED COM1, COM2, printer port, built in VGA.

I am using a Diamond Stealth64 2MB VRAM in a pci slot.

I have tried using the Novell/Anthem NE2000 compatibale device driver (and a few others that are supposed to be NE2000 clones). All with the same results.

When I boot I get the message "Your network adaptor Novell/Anthem NE2000(0000) is not working properly. You may need to set it up again. For more information see the Network Trouble shouter in Windows Help.

After I click OK the boot finishes. In Device Manager no nic is listes. I click Refresh and the nic appears. At that point I can use my lan with no problem.

I assume there is some sort of misque between the nic and the device driver at boot that is not an issue during the refresh.

Any ideas? I gotta believe there is a minor registry tweak that will fix this. I would be satisfied if there is a way to script doing the Device Manager Refresh automatically after boot.

Also, the NS 8390 chip on this card is the same as on a lot of other cards, such as 3c503. Does anyone know if there are 32bit device drive drivers for some other card that might work for this one? It seems that I can only find drivers specifically for these cards that are for 3.1 or 3.11. Yeah, thier that old.

Again, thanks to everyone willing to take on this challange.
 
There is a UTILITY called PlusDiag that you need to use to configure
the card to use the IRQ you choose (much like 3com's PNP enabling utility).

Do a search on Google and you should be able to locate it.
 
thanks LiLithTecH.

This card has jumpers for Irq and i/o. Should I still use the utility?
 
Yes. You need the Utility to properly setup the card as I remember it.

The default setting should have been IRQ3 300h, and worked most of the time.

The Utility has onboard Diagnostic feature to search for a proper I/O address that
is available. (you cannot have the driver installed or the utility will not function)
 
Back
Top