last updated at 01 Nov, 2005 07:14 (1 times)
It isn't too difficult, just takes a bit of work:1. Obviously, you'll need to have DOS and WinOS/2 support installed.
2. Next, you'll need to have the DOS and WinOS/2 TCP/IP stuff installed (This should be default in most versions of Warp. Check to see if you have a c:\tcpip\dos directory) See if WINSOCK.DLL is in the c:\tcpip\dos\bin directory. (Of course, the c: part could be a different drive, if TCPIP is installed on another drive)
3. Check your autoexec.bat file, make sure it has the c:\tcpip\dos\bin in the PATH statement
4. Check your autoexec.bat file, and make sure the SET ETC variable is set - in my file, I have SET ETC=C:\TCPIP\DOS\ETC
5. Check the RESOLV file in C:\TCPIP\DOS\ETC it should have domain and name server information in it, for example:
domain.anydomain.com
nameserver xx.xx.xxx.xx
nameserver xx.xx.xxx.xx
For the name server information, you can probably find it in your c::\mptn\etc\resolv2 or c:\mptn\etc\resolv file. Or check for the information with your ISP. If you're using dialup, you usually get this information with your PPP authentication.
Fire up WinOS/2 and see if it works. There is a wping.exe application which you can try - a Windows 3.1 Ping app. If it works and you can ping somewhere, then you should be good to go.
What I've done to make sure my resolv file is always up to date, is I've added the following line to my autoexec.bat file:
copy c:\mptn\etc\resolv2 c:\tcpip\dos\etc\resolv
That way, each time I fire up WinOS/2 or a Dos box, it will update the name server information so it is correct - even if my cable company changes this information on a DHCP lease update.
Hope this helps.