WinOS2 and WinSock

[Neil Waldhauer]

I installed some Win16 networking application, and I realized that it won't work without some kind of WinSock support.

 https://mochasoft.dk/win311x.htm

Apparently I've forgotten how to add WinSock support. Anyone remember this one?

[Dave Yeo]

It might be as simple as adding x:\TCPIP\dos\bin to the PATH in autoexec.bat, but it has been a long time and there might have needed to be a setting on system.ini or win.ini.

[Neil Waldhauer]

Thanks, I see I have winsock, and it's in the path. Something else is wrong.

While I'm at it, I'm trying to get TN5250 to work. Maybe getting these old 16-bit Win freeware programs isn't the best way. What other ways could I get TN5250 capability. (Telnet to an IBM iSeries)

[David McKenna]

 Hi Neil,

 If I remember correctly, installing the MS Internet Explorer for Win3.1 will also install and setup winsock support. There was also 'Trumpet Winsock' that was used before IE. Been a loong time tho.... gotta try this again myself...

Regards,

[Neil Waldhauer]

Thanks for the tip.

I tried installing IE from a WinOS2 Full Screen session, and the OS/2 system traps. I have auto-ipl, so I didn't even get to see the trap screen.

The readme for 16-bit IE says you must install your own WinSock.

[Dave Yeo]

Try installing Trumpet Winsock from http://trumpet.com.au/index.php/downloads.html. It's good for a 30 day evaluation. Might want to back up your Winos2 install first just in case.
I used it when I first moved to OS/2 v3 (redbox) to dial in from Win 3.1 and it worked fine. The IBM Winsock was pretty broken until Netscape helped fix it. Still don't remember much about setting it up.

[Bogdan]

I installed some Win16 networking application, and I realized that it won't work without some kind of WinSock support.

 https://mochasoft.dk/win311x.htm

Apparently I've forgotten how to add WinSock support. Anyone remember this one?

There is no reason for adding the support. It should be available from IBM TCP/IP for OS/2 by default (VDOSTCP.SYS). Only configuration for \TCPIP\dos\etc\RESOLV should be done.

[Dave Yeo]

There is no reason for adding the support. It should be available from IBM TCP/IP for OS/2 by default (VDOSTCP.SYS). Only configuration for \TCPIP\dos\etc\RESOLV should be done.

Windows programs usually link to Winsock for TCPIP excess.

[Neil Waldhauer]

I heard that I needed to run two programs to get the IBM WinOS2 TCP/IP support working better.

1. Run \MPTN\BIN\VDOSCTL.EXE

2. Inside WinOS2, run \TCPIP\DOS\BIN\TCPCNTL.EXE

After doing those two things, the Mocha telnet is working. I did not yet try the TN5250 or TN3270, but I'll bet they work fine, too.

The only thing wrong is that on my SMP system, all cores are working at 100%. Does anyone know if there is a DOS Setting that controls programs that hog the CPU by polling?

[Heikki Kekki]

I heard that I needed to run two programs to get the IBM WinOS2 TCP/IP support working better.

1. Run \MPTN\BIN\VDOSCTL.EXE

2. Inside WinOS2, run \TCPIP\DOS\BIN\TCPCNTL.EXE

After doing those two things, the Mocha telnet is working. I did not yet try the TN5250 or TN3270, but I'll bet they work fine, too.

The only thing wrong is that on my SMP system, all cores are working at 100%. Does anyone know if there is a DOS Setting that controls programs that hog the CPU by polling?

IDLE_SENSITIVITY, default is 75, usually I put it to 4 or 5 for DOS programs.

[Neil Waldhauer]

I cannot completely fix this with IDLE SENSITIVITY. While telnet works, the system is stressed doing it. I also have occasional traps. I suggest this isn't really useful software on OS/2.

In the meantime, someone suggested that I try ZOC 4.15, and that does appear to have TN 5250 in it.