Are you sure that the PN-16 config utility is generically applicable to all UM9007 cards?
It looks quite different than your card. https://vogonsdrivers.com/getfile.php?fileid= … 778&menustate=0
Also, it's not clear how it knows whether another IRQ conflicts or not. Is it checking whether anything has the vector for that IRQ hooked in the IVT? Does it have a hardcoded list saying if port 2f8h reads back then IRQ3 must be taken? etc. This is not generally possible with plain ISA.

jakethompson1 wrote on 2026-06-20, 19:46:

Are you sure that the PN-16 config utility is generically applicable to all UM9007 cards?
It looks quite different than your card. https://vogonsdrivers.com/getfile.php?fileid= … 778&menustate=0
Also, it's not clear how it knows whether another IRQ conflicts or not. Is it checking whether anything has the vector for that IRQ hooked in the IVT? Does it have a hardcoded list saying if port 2f8h reads back then IRQ3 must be taken? etc. This is not generally possible with plain ISA.

It's a pretty generic UM9007 utility. This card does look physically different, but the controller chip determines behaviour. In any event the issues sound about right for an IRQ conflict, so for now I'd certainly roll with that hypothesis until disproven.

The likelihood that IRQs 9, 10, and 11, far more sensible choices for an ethernet card than 5 or 3, all have some card set to them *and* are actively in use in DOS such that this utility can even detect that, is very slim.
It might be worth trying HWINFO from here on the forum though. It should know about both ISAPNP as well as its known non-PNP cards it can probe for, and help identify what might be using these IRQs.

IRQ5 was default for XT Ethernet, but if no IRQs are reserved in BIOS, any IRQ could be in use for any (onboard) PnP device. So it doesn't matter which IRQ the card is set to, so long as that IRQ is reserved.

The XT hard disk controller is IRQ 5 so that would be an unfortunate choice. In any case, I hope OP has already tried cleaning the card's edge connector with a pencil eraser.

Is a test program for a dp8390 truly compatible with a umc um9007 ?

jakethompson1 wrote on 2026-06-20, 20:05:

In any case, I hope OP has already tried cleaning the card's edge connector with a pencil eraser.

This!
Or simply remove and insert the card again, a few times.

This way, I've "repaired" stuff too many times to even count - oxydation is normal for something that was hidden in storage for years and decades...

I've had the same issue sometime with my NE2000. Removing all cards, changing the ISA bus, altering the IRQ (it's not PnP, I have to set jumper less with rst8019.exe utility) worked to me.
Of course, card slot should be cleaned.

Disruptor wrote on 2026-06-20, 17:37:

Try to remove as many cards as possible to get your network card running. Set media type to UTP (not auto-detect). Boot without […]
Show full quote

Try to remove as many cards as possible to get your network card running.
Set media type to UTP (not auto-detect).
Boot without config.sys / autoexec.bat and run the config utility.

Try another slot.

First thing is to get success in the config utility.
Windows 95B just need himem.sys to be loaded, and DOS=HIGH

Tried with only HDD controller, GFX and NIC. Controller's COM2 and LPT1 disabled.
Media type can't be changed in the utility.
NIC tested in three or four slots I think.

Setup menu gets into a loop of IRQ 3 > 4 > 3 > 4 (sometimes also IRQ 5) suggestion for every restart.
Autoinst.exe says "Cannot find the PN-16 Series Ethernet Adapter"

dionb wrote on 2026-06-20, 19:39:

IRQ issues... that makes sense. […]
Show full quote

IRQ issues... that makes sense.

Quick check on BIOS settings:
- what's PnP OS set to? Recommend "No"
- when you set the card to an IRQ, do you also reserve that IRQ for "ISA/Non-PnP" in BIOS? If not, try that.

I'm a bit amazed by this AMI Bios. It offers lots of options for memory timings and cache altering, but no selection of IRQ or PnP - very stripped down.

Thanks for all replies! Only now saw there was another page here.

jakethompson1 wrote on 2026-06-20, 20:05:

The XT hard disk controller is IRQ 5 so that would be an unfortunate choice. In any case, I hope OP has already tried cleaning the card's edge connector with a pencil eraser.

Isn't IRQ 5 standard for Creative cards?

I did test this card in another PC, with an UM9008 already installed and working (replaced it with this for testing).
Same behaviour in that machine.
Connectors cleaned with isopropanol.

Ahrle wrote on Yesterday, 08:35:

I'm a bit amazed by this AMI Bios. It offers lots of options for memory timings and cache altering, but no selection of IRQ or PnP - very stripped down.

It seems you're using a pre-PCI motherboard - they don't have any PnP options.
But they also don't have any integrated devices that might occupy any IRQ - especially IRQ 10 is sure to be free.

So, the revised procedure would be:
- remove the SB, and other unnecessary cards
- use pure DOS, "Command prompt only" is OK, with CONFIG.SYS and AUTOEXEC.BAT as empty as possible
- set the NIC to I/O 300h, IRQ 10
- if the config program complains about that IRQ, simply ignore it
- load the packet driver: ne2000 0x60 10 0x300
- see if it receives something: pkttool listen 0x60 -v