Winsock Help: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
From [[Judy's Warped World]]
{{Article
|Author=
|Date=
|OS=OS/2 Warp 3, 4.0
|File=
|Source=[[Judy's Warped World]]
}}
This setup will allow you to use Window clients in WIN-OS/2 with Warp 3.0, Warp 3.0 Connect and Warp 4.0, if you must. Warp 3.0 Connect will use the same instructions for *Warp 4.0.
 
1.- Check your config.sys. No statement that supports DOS can be REM'ed out.


This setup will allow you to use Window clients in WIN-OS/2 with Warp 3.0, Warp 3.0 Connect and Warp 4.0, if you must. Warp 3.0 Connect will use the same instructions for *Warp 4.0.
2.- There can only be 1 active winsock.dll. The IAK (Internet Access Kit), included in the OS/2 Warp Bonus Pak, installs winsock.dll in the x:\tcpip\dos\bin subdirectory. (Unsure if you have more than 1? Do a find winsock.dll)


#Check your config.sys. No statement that supports DOS can be REM'ed out.
3.- Create a file and save as resolv (no it's not a typo, there's no e...just resolv) The file will consist of the following 2 lines: (your domain name ie. oeonline.com & nameserver IP address ie. 205.199.95.66)
#There can only be 1 active winsock.dll. The IAK (Internet Access Kit), included in the OS/2 Warp Bonus Pak, installs winsock.dll in the x:\tcpip\dos\bin subdirectory. (Unsure if you have more than 1? Do a find winsock.dll)
#Create a file and save as resolv (no it's not a typo, there's no e...just resolv) The file will consist of the following 2 lines: (your domain name ie. oeonline.com & nameserver IP address ie. 205.199.95.66)
  domain oeonline.com
  domain oeonline.com
  nameserver 205.199.95.66
  nameserver 205.199.95.66
#Copy the resolv file to the x:\tcpip\etc & x:\tcpip\dos\etc subdirectories.
 
4.- Copy the resolv file to the x:\tcpip\etc & x:\tcpip\dos\etc subdirectories.
:; Warp 4.0:
:; Warp 4.0:
;Copy resolv file to x:\mptn\etc
;Copy resolv file to x:\mptn\etc
#Add the following statement to the autoexec.bat
 
5.- Add the following statement to the autoexec.bat
  SET ETC= x:\tcpip\dos\etc
  SET ETC= x:\tcpip\dos\etc
:; Warp 4.0:
:; Warp 4.0:
  SET ETC=x:\mptn\etc
  SET ETC=x:\mptn\etc
#Add the following to the PATH= statement in autoexec.bat (this points to the winsock.dll)
 
6.- Add the following to the PATH= statement in autoexec.bat (this points to the winsock.dll)
  x:\tcpip\dos\bin;
  x:\tcpip\dos\bin;


; Netscape Tips for Warp 3.0 and Warp 4.0
==Netscape Tips for Warp 3.0 and Warp 4.0==


I've had success in runnning the 16bit versions of Netscape with Warp 3.0 and Warp 4.0.
I've had success in running the 16bit versions of Netscape with Warp 3.0 and Warp 4.0.


Obtain the Windows 16bit version only. OS/2 Warp will not run the 32bit version of Netscape. (32bit version is used with Windows 95 and Windows NT which have a 32bit TCP/IP stack)
1.- Obtain the Windows 16bit version only. OS/2 Warp will not run the 32bit version of Netscape. (32bit version is used with Windows 95 and Windows NT which have a 32bit TCP/IP stack)


Run in standard mode - enhanced mode is not necessary, unless you install Real Audio, then you will need to run both Netscape and Real Audio in Enhanced mode.
2.- Run in standard mode - enhanced mode is not necessary, unless you install Real Audio, then you will need to run both Netscape and Real Audio in Enhanced mode.


Obtain the file ic11173.zip. This file contains the files vdebug.exe, vdosctl.exe and vdostcp.vdd, Do not use the vdostcp.vdd from ic11173.zip, ic14468.zip contains a newer version that you will use.
3.- Obtain the file ic11173.zip. This file contains the files vdebug.exe, vdosctl.exe and vdostcp.vdd, Do not use the vdostcp.vdd from ic11173.zip, ic14468.zip contains a newer version that you will use.


;ic11173.zip
;ic11173.zip


Unzip ic11173.zip into a temporary directory and reboot.
4.- Unzip ic11173.zip into a temporary directory and reboot.


When the white box appears in the left corner of the screen, hit alt+f1, then go to an OS/2 prompt.
5.- When the white box appears in the left corner of the screen, hit alt+f1, then go to an OS/2 prompt.


Go to the x:\tcpip\bin subdirectory and rename the files vdosctl.exe and vdebug.exe.
6.- Go to the x:\tcpip\bin subdirectory and rename the files vdosctl.exe and vdebug.exe.


Copy the replacement files that you unzipped in the temporary directory to the x:\tcpip\bin subdirectory.
7.- Copy the replacement files that you unzipped in the temporary directory to the x:\tcpip\bin subdirectory.


Type exit at the prompt and machine will reboot
8.- Type exit at the prompt and machine will reboot


Download the file ic14468.zip
9.- Download the file ic14468.zip
:; Warp 4.0:
:Follow the instructions below.


; Warp 4.0:
10.- Rename the vdostcp.vdd in the x:\tcpip\bin subdirectory and replace with the new file.
Follow the instructions below.


Rename the vdostcp.vdd in the x:\tcpip\bin subdirectory and replace with the new file.
11.- Rename the winsock.dll in x:\tcpip\dos\bin subdirectory and replace with the new file.


Rename the winsock.dll in x:\tcpip\dos\bin subdirectory and replace with the new file.
12.- A reboot isn't needed.
A reboot isn't needed.


May run in full-screen or windowed session. I prefer running in a seamless windowed session. Setup an object on the wps (workplace shell, OS/2's desktop), go into settings/session, select WIN/OS/2-window.
13.- May run in full-screen or windowed session. I prefer running in a seamless windowed session. Setup an object on the wps (workplace shell, OS/2's desktop), go into settings/session, select WIN/OS/2-window.


If you are still having problems running Netscape after following the above Winsock Set-up, you may try changing the settings in the Netscape.ini:
14.- If you are still having problems running Netscape after following the above Winsock Set-up, you may try changing the settings in the Netscape.ini:
  [Network]
  [Network]
  Use Async DNS=no
  Use Async DNS=no
  Max Connections=1
  Max Connections=1


; Removing Win32s
==Removing Win32s==
 
1.- Remove the following line from the [386Enh] section in the SYSTEM.INI file device=<WINDOWS>\<SYSTEM>\win32s\w32s.386
Remove the following line from the [386Enh] section in the SYSTEM.INI file device=<WINDOWS>\<SYSTEM>\win32s\w32s.386
where <WINDOWS> and <SYSTEM> are where the Windows and System directories are, respectively.
where <WINDOWS> and <SYSTEM> are where the Windows and System directories are, respectively.


Remove WINMM16.DLL from the following line from the [BOOT] section in the SYSTEM.INI file:
2.- Remove WINMM16.DLL from the following line from the [BOOT] section in the SYSTEM.INI file:
  DRIVERS=MMSYSTEM.DLL WINMM16.DLL
  DRIVERS=MMSYSTEM.DLL WINMM16.DLL


Delete the following files from the <WINDOWS>\<SYSTEM> subdirectory:
3.- Delete the following files from the <WINDOWS>\<SYSTEM> subdirectory:
* W32SYS.DLL
* W32SYS.DLL
* WIN32S16.DLL
* WIN32S16.DLL
* WIN32S.INI
* WIN32S.INI
Delete all the files in the <WINDOWS>\<SYSTEM>\WIN32S subdirectory. Then delete the subdirectory itself.
4.-Delete all the files in the <WINDOWS>\<SYSTEM>\WIN32S subdirectory. Then delete the subdirectory itself.


Restart Windows.
5.-Restart Windows.


If you have any problems, e-mail me with the specific problem and I will attempt to offer assistance. Or stop by the #os/2 irc channel, there's always lots of folks willing to help.
If you have any problems, e-mail me with the specific problem and I will attempt to offer assistance. Or stop by the #os/2 irc channel, there's always lots of folks willing to help.


[[Category:Dump]]
[[Category:Network‎]]

Latest revision as of 15:50, 10 October 2021

Article Info
Author
Date
OS Version OS/2 Warp 3, 4.0
Companion File
Source Judy's Warped World

This setup will allow you to use Window clients in WIN-OS/2 with Warp 3.0, Warp 3.0 Connect and Warp 4.0, if you must. Warp 3.0 Connect will use the same instructions for *Warp 4.0.

1.- Check your config.sys. No statement that supports DOS can be REM'ed out.

2.- There can only be 1 active winsock.dll. The IAK (Internet Access Kit), included in the OS/2 Warp Bonus Pak, installs winsock.dll in the x:\tcpip\dos\bin subdirectory. (Unsure if you have more than 1? Do a find winsock.dll)

3.- Create a file and save as resolv (no it's not a typo, there's no e...just resolv) The file will consist of the following 2 lines: (your domain name ie. oeonline.com & nameserver IP address ie. 205.199.95.66)

domain oeonline.com
nameserver 205.199.95.66

4.- Copy the resolv file to the x:\tcpip\etc & x:\tcpip\dos\etc subdirectories.

Warp 4.0
Copy resolv file to x
\mptn\etc

5.- Add the following statement to the autoexec.bat

SET ETC= x:\tcpip\dos\etc
Warp 4.0
SET ETC=x:\mptn\etc

6.- Add the following to the PATH= statement in autoexec.bat (this points to the winsock.dll)

x:\tcpip\dos\bin;

Netscape Tips for Warp 3.0 and Warp 4.0

I've had success in running the 16bit versions of Netscape with Warp 3.0 and Warp 4.0.

1.- Obtain the Windows 16bit version only. OS/2 Warp will not run the 32bit version of Netscape. (32bit version is used with Windows 95 and Windows NT which have a 32bit TCP/IP stack)

2.- Run in standard mode - enhanced mode is not necessary, unless you install Real Audio, then you will need to run both Netscape and Real Audio in Enhanced mode.

3.- Obtain the file ic11173.zip. This file contains the files vdebug.exe, vdosctl.exe and vdostcp.vdd, Do not use the vdostcp.vdd from ic11173.zip, ic14468.zip contains a newer version that you will use.

ic11173.zip

4.- Unzip ic11173.zip into a temporary directory and reboot.

5.- When the white box appears in the left corner of the screen, hit alt+f1, then go to an OS/2 prompt.

6.- Go to the x:\tcpip\bin subdirectory and rename the files vdosctl.exe and vdebug.exe.

7.- Copy the replacement files that you unzipped in the temporary directory to the x:\tcpip\bin subdirectory.

8.- Type exit at the prompt and machine will reboot

9.- Download the file ic14468.zip

Warp 4.0
Follow the instructions below.

10.- Rename the vdostcp.vdd in the x:\tcpip\bin subdirectory and replace with the new file.

11.- Rename the winsock.dll in x:\tcpip\dos\bin subdirectory and replace with the new file.

12.- A reboot isn't needed.

13.- May run in full-screen or windowed session. I prefer running in a seamless windowed session. Setup an object on the wps (workplace shell, OS/2's desktop), go into settings/session, select WIN/OS/2-window.

14.- If you are still having problems running Netscape after following the above Winsock Set-up, you may try changing the settings in the Netscape.ini:

[Network]
Use Async DNS=no
Max Connections=1

Removing Win32s

1.- Remove the following line from the [386Enh] section in the SYSTEM.INI file device=<WINDOWS>\<SYSTEM>\win32s\w32s.386 where <WINDOWS> and <SYSTEM> are where the Windows and System directories are, respectively.

2.- Remove WINMM16.DLL from the following line from the [BOOT] section in the SYSTEM.INI file:

DRIVERS=MMSYSTEM.DLL WINMM16.DLL

3.- Delete the following files from the <WINDOWS>\<SYSTEM> subdirectory:

  • W32SYS.DLL
  • WIN32S16.DLL
  • WIN32S.INI

4.-Delete all the files in the <WINDOWS>\<SYSTEM>\WIN32S subdirectory. Then delete the subdirectory itself.

5.-Restart Windows.

If you have any problems, e-mail me with the specific problem and I will attempt to offer assistance. Or stop by the #os/2 irc channel, there's always lots of folks willing to help.