Check Open Watcom 1.9 bugs against Open Watcom 2.0 fork

[davidrg]

The OS/2 version of Kermit 95 is affected by a number of bugs in the Open Watcom 1.9 compiler, runtime library and headers:

• Optimised watcom OS/2 builds crash on startup #55
• Building with NetBIOS enabled causes a crash on startup #56
• Fix conkbg() in ckotio.c for OpenWatcom on OS/2 #58
• calling ck_sockinit() in cko32i20.dll on OS/2 Warp 3 with the internet connection kit, OS/2 Warp 3 Connect, and OS/2 Warp 4 Server, and OS/2 Warp 4 causes a stack overflow when no fix packs are installed. This happens even when SOCKS support in cko32i20.dll is disabled turning ck_sockinit() into a trivial function that just calls sock_init() in the IBM TCP/IP stack.
  • The same DLL from Kermit 95 2.1.2 works fine without any fix packs suggesting the issue may be cause by Open Watcom in some way
  • cko32i20.dll built with Open Watcom is confirmed to work on OS/2 Warp 4 FP15 and OS/2 2.11 with IBM TCP/IP 2.0, so the issue is specific to Warp 3
  • Building with -s or -sg turns out to be the fix.

And these may also be bugs in the compiler or runtime:

• Making or receiving a NetBIOS connection on OS/2 crashes K95 #368
• The Dialer on OS/2 crashes on startup #152

Workarounds have been put in place for some of these (described in the tickets and/or commit messages). If Open Watcom 2.0 isn't affected by these issues, it would be good to make the workarounds specific to Open Watcom 1.9 and older.

And if Open Watcom 2.0 is affected by them still, then they probably should be reported so they can be fixed.