1
Hardware / Re: [Solved] Xircom - PCMCIA Ethernet - Thinkpad - OS/2 Warp 3 Connect
« on: November 08, 2025, 08:14:20 pm »
Sure, no problem at all. Protocol.ini attached.
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
@RTAN - Great suggestion. I have FTP running on the NAS but do like the option of having the FTP server run on OS/2.
@LARS - Waiting on the dongle to arrive, eta is Friday. Once I get that I will follow the instructions you have posted and report back. Thank you for putting the time and work into this.
@Steven - Thank you for linking to the driver.
Sorry for the late reply, had some hardware issues on the Thinkpad. The original drive died so I replaced with a flash card. The Xircom dongle also seems to be defective. I installed on a Windows 98 laptop and got the drivers installed but was getting inconsistent pings at the slightest touch of the dongle.
@Martin - I downloaded the drivers you posted, need to get a dongle to test. Thank you.
In case you want to retry your CE2 card with the driver set that Martin provided (say "FIN-XIR2.ZIP"):
the .NIF installation file would need a "brush up" to actually install the proper entries into the PROTOCOL.INI file.
Gleaning at the driver binary (CE2NDIS.OS2) and other .NIF files from Xircom, I think I would be able to provide you with a fixed .NIF file.
I can also see that even with the CE2NDIS.OS2 driver (and a corrected .NIF file), you will be able to ignore socket services and run the driver in "point enabled" mode which would allow you to always have PCMCIA support installed. If set up correctly via PROTOCOL.INI, the driver will just ignore/bypass the card services.
@Martin: would you see any issues in uploading these drivers to Hobbesarchive ? I am not the legal expert ...
Can you post your setup.cmd and also protocol.ini ?
The error does not sound as if this is HW or driver related. It rather sounds like TCP/IP not being set up correctly.
By the way: you might also consider applying the patch to the NDIS driver:
https://www.os2site.com/sw/drivers/network/3com/3c589patch.zip
That might not strictly be necessary on your system but it surely won't hurt either. In addition, it will make the "3net_log.exe" utility work.
Finally, look here, it is about Warp 4 but since you are using Warp 3, it might apply nonetheless:
https://www.os2world.com/olderforum/OS2World%20Ultraboard/www.os2world.com/cgi-bin/ultraboard/UltraBoardea6e.html?action=Print&BID=62&TID=1518&SID=