For your installation issues, it sounds like you need to create updated installation disks. This topic has been covered quite a few times in this forum, do a quick search and you should be able to find an answer. However I should point out that it may not be necessary to do a full blown install, if you are just trying to go from a currently running Warp 3 to Warp 3 connect.Do you currently have Warp 3 installed at the latest public fixpak level (Fixpak 40)? If so, then upgrading to Warp 3 Connect is easier then you'd think.
The only difference between Warp 3 Connect and Warp 3 (when it has a current fixpak) is the networking stuff. You can install just the networking stuff from the Warp Connect CD Rom. Here's how.
If you currently have installed the IBM Internet Access Kit (the dialup only one), then rename your c:\tcpip directory (rename it to something like c:\tcpipold - Warp 3 Connect installs a newer version of TCP/IP, which if memory serves, sometimes has trouble with the older version included in the IAK), remove any references to c:\tcpip from your config.sys (keep a backup of your current config.sys in case something doesn't work), restart your computer, and then you can just run the networking installation stuff from the Warp 3 Connect CD.
You can do a straight install of the networking stuff by running an install found on the Warp 3 Connect CD Rom:
x:\install.cmd
where x: is the drive letter of your CD ROM. This will kick in the LAN installation stuff.
The main reason that the Warp Connect manual suggests running the full-blown installation is because Warp Connect shipped at a later fixpak level then the original Warp 3 (non-connect), and some of the networking stuff didn't work properly without the later base fixpak (I think Warp Connect shipped at the Fixpak 5 level). But as long as you're running with a current fixpak on Warp 3 (Fixpak 40 is the last one that IBM released to the public for Warp 3 Connect), you'll be fine.
Once you get the networking stuff installed, you'll want to update the TCP/IP, MPTS, and IBM Peer (if you've installed Peer) to the latest fixpak levels for those components.
For TCP/IP, you'll want UN00959 at:
ftp://service.boulder.ibm.com/ps/products/tcpip/fixes/v3.1os2/un00959/english-us/
MPTS WR08423_conv and then WR08425:
ftp://service.boulder.ibm.com/ps/products/mpts/fixes/english-us/wr08423_conv/
ftp://service.boulder.ibm.com/ps/products/mpts/fixes/english-us/wr08425_conv/
IBM Peer ip08196:
ftp://service.boulder.ibm.com/ps/products/lan/fixes/ibm.peer/english-us/ip08196/
Alternatively, if you want to update TCP/IP to the 32 bit stack, you'll need to install wr08610_conv, then wr08621, and then newstack.zip instead of the wr_08423 and wr08425:
ftp://service.boulder.ibm.com/ps/products/mpts/fixes/english-us/wr08610_conv/
ftp://service.boulder.ibm.com/ps/products/mpts/fixes/english-us/wr08621/
http://hobbes.nmsu.edu/cgi-bin/h-search?key=newstack.zip&pushbutton=Search
Note that for the 32 bit TCP/IP stack to work, you *must* install the UN00959 fixpak from above!