🚀 go-pugleaf

Hello All:
Previously I'd posted that I was having difficulty using the
32-bit Drivers in Client 32 DOS/Windows with IBM NICs.
Thanks to the responses I received, I am now able to use
the "Novell Token-Ring" option which is selectable in the
Windows Installation. THANKS!

Unfortunately, I am still having a problem with one of the
flavors (so far) of the IBM NIC, the "Auto 16/4 Token Ring
ISA" (which can be identified by its having two LEDs on the
back, one RJ-45 jack, and is shipped with IBM's LANAID
utility. I've been unsuccessful in using Client 32 with this
NIC. When CNTR2000.LAN (as per the Novell Token-Ring selection
above) tries to load, I receive the error:

020: AN INTERRUPT FAILED TO OCCUR DURING INITIALIZATION...
MODULE C:\NET\NWCLIENT\CNTR2000.LAN DID NOT REMAIN RESIDENT

and, I'm unable to access the network.

Additionally, I'm unable to run the 16-bit drivers of
Client 32, as the card hangs (most noticeably when TCPIP.NLM
loads, but even when I take that line out and I can reach the
Login Prompt, after I type my Login Name, the PC hangs).

I've tried using the IBM LANAID utility to manually try
various Interrupt, ROM Address, and RAM Address configurations
unsuccessfully.

I've also examined IBMLAN.EXE (Drivers for 4.11), but there
are only 3 *.LAN Drivers (two for Ethernet and one PCI
Token-Ring...I can't use any of these...). And the TOKEN.COM
(16-bit) included is the same as I have.

These NICs are in Dell Pentium-based OptiPlex PC's....I don't
know if this is the problem....I'm still troubleshooting....
but....

If anyone has successfully implemented 32-bit (preferably) or
16-bit Novell Client 32 DOS/Windows with the IBM Auto 16/4
Token Ring ISA NIC, I'd be grateful if you could share your
configuration secrets with me.

Thanks to all.
Steve Sathue
sathuest@tokiom.com