Windows applications get their TCP/IP support through a library of services called WINSOCK.DLL. Warp has WINSOCK support for Windows applications. To make sure that it is enabled, check your CONFIG.SYS for the following lines:

 DEVICE=f:\tcpip\bin\vdostcp.vdd
 DEVICE=f:\tcpip\bin\vdostcp.sys
 RUN=f:\tcpip\bin\cntrl.exe
 RUN=f:\tcpip\bin\vdosctl.exe

This will insure that you have global tcp/ip support in your DOS and Windows sessions. If you are running Warp 4 or Warp Connect cntrl.exe will be in \mptn\bin, not \tcpip\bin.

In \tcpip\dos\bin make sure that there is WINSOCK.DLL. Make sure that \tcpip\dos\bin is in the PATH statement of the AUTOEXEC.BAT that OS/2 uses to start DOS and Win-OS/2 sessions with. Also, make sure that the AUTOEXEC.BAT includes the following statement:

  SET ETC=f:\tcpip\dos\etc

(pointed to the appropriate drive on your system)

Finally, make sure that if there is any other WINSOCK.DLL on your system, it is not in a directory in the PATH where it would be found before the one in \tcpip\dos\bin.

When you are ready to run your Windows application, start your OS/2 Internet connection. When the connection is established, start the Windows application.

You can test that everything is set up correctly by using WPING.EXE that is in \tcpip\dos\bin. If WPING will resolve addresses, such as compuserve.com to numeric IP addresses the you've got everything working right.

If things are not working right, check the settings for the Win-OS/2 program object you are running to see if the DOS_DEVICE setting includes \TCPIP\BIN\VDOSTCP.SYS. The DEVICE= statement described earlier in this message should cause DOS_DEVICE to be set to \TCPIP\BIN\VDOSTCP.SYS. However, program objects that were created before you enable TCP/IP support for DOS and Win-OS/2 may not get updated.