Well after a few changes, I'm getting promising signs (but not there yet).

I am using XWLAN v 3.0 and Genmac v 2.01.

I think the turning point was NOT to have the TCPIP interface defined and active in TCPCFG2, rather to let XWLAN create the connection. (earlier versions of Genmac/XWLAN I could only get to work by having the second interface defined nd configured in TCPCFG2).

Now however, when I boot the system it makes a whole series of fault tones for about 30 seconds while XWLAN is loading and then pops up the IP range conflict error asking me whether I want LAN0 (the cabled connection) nullifying so that Wifi can operate. Selecting yes here unfortunately does not allow the WiFi to operate, rather it gives a red bars symbol indicating that I am out of range of my WiFi access point, which happens to be about 2 metres away.

To me this looks and sounds like an IRQ conflict, possibly with audio.

Do we still have a problem with UniAud ? As of course the eCS install, installed UniAud rather than the OS/2 driver for the on-baord audio chipset.

I'll try disabling UniAud and see how WiFi works then.

Apparently there is a later version of the UniAud DLL (needed by the latest WarpVision build among other things) - perhaps that'll solve the problem as well.

Cheers/2

Ed.