.....
However, the network still does not work. I tried using DHCP or a static IP address, it makes no difference and it looks like no packets are sent out or nothing is received.
I would test the network with ifconfig lan0 or ifconfig lan1 (depends on how many network cards you've configured).
f.i. issuing from a command line 'ifconfig lan0 192.168.1.1' results in 'sioaffc error' (or similar) or 'interface not available' the driver does not work and no need to play with tcpcfg2 any further. Might save you some time....
I looked carefully at the config.sys file from ThinkpadConfig.zip.
There's one line there, which looks like a point enabler:
DEVICE=E:\OS2\BOOT\AUTODRV2.SYS E:\OS2\AUTODRV2.INI
Andi, do you still have the contents of your AUTODRV2.INI anywhere?
I've very little knowledge about this PCMCIA stuff but always thought AUTODRV is necessary for Flash drives or maybe cards which are configured by the card services which is
NOT the case with
MY Xircom. I'm rather sure this entry does have nothing to do with my Xircom as my Xircom seems to be one of the 'PointEnabler' types. I can post this file when at home but most likely there is nothing in there for the Xircom.
In version 5 of PC Card Director (this is what I got), AUTODRV2.SYS is loaded by BASEDEV, not DEVICE, and the documentation does not mention any parameters that can be specified, so I'm not sure it this is a good route to go, but perhaps it is worth giving it a try.
As for specifying the /s0= parameter for IBM2SS01.SYS, this did not work. First of all, the file I got with PCCard Director is named a bit differently, IBM2SS14.SYS. And it does not accept /s0=, saying "invalid parameter specified" during boot.
So, currently I try to use the driver without any socket and card services, and my config.sys file looks like this:
Remember my setup is a Warp3 with I think no fixpacks but Lan Server 4.0 components on top. So I don't know which PCCard Director / Ezlite version is installed there. And my Xircom seems to be a different one as yours.
...
The next thing I'm going to do is to use AUTODRV2.SYS (point enabler) which came with PCCardDirector 5. The documentation says that custom scripts can be prepared, so I'm going to give it try. This might not be easy though, as I'm not sure I know what I'll be doing ...
As usual, any suggestions will be appreciated
Peter
If your card could not be controlled by PCCard Services, which is much likely with Xircoms, then I think the key is to disable the correct slot in card services (/S0=1 /IG0=1 --- not sure anymore what each param does and how it works with v5.0).
One drawback with the Xircom I remember is that power management will not work (no Hibernate). So for the Thinkpad I setup a few weeks ago I used a 3Com card. Even with the 3Com it took me hours (and an old TP380 Thinkpad on which the DOS utility will run cause on the T41 it crashes) to get it to work.
Once I had a Xircom user manual where the steps for setting up with OS/2 are described. But now only found one version without any OS/2 references anymore. To bad it seems I've lost the other one...