-> Warp 3 Connect, under VMworkstation with SIO.  It took me the better   
   -> part of 8 hours to get OS/2 to load and run under VMworkstation   
      
   I couldn't get WARP 4 installed on VMware workstation. Sometime during   
   the install all screen and disk activity stopped. After 10 minutes of no   
   progress, I gave up.   
      
   Virtual PC 2004 worked though. Done in less than an hour. I suppose VPC   
   2007 would work too. Changing floppy images and ISOs during the initial   
   stages of install is easy with VPC; VMware is clumsy in comparision.   
      
   I find that MCP2 has problems connecting to a WinXP share; it's very   
   slow to connect, and once you disconnect it fails to reconnect without   
   rebooting. The peer networking in WARP 4 does not have that problem.   
   Connects and reconnects just fine.  Quick too.   
      
   So I mixed and matched (reboot after each step):   
      
   a) install MCP2 without networking (you are forced to install at least   
   MPTS, just do it with no adapter)   
      
   b) remove MPTS   
      
   c) install MPTS from WARP 4 (find the \CID\IMG directory on the CDROM),   
   with your adapter of choice and only one protocol, TCP; do NOT configure   
   TCP when prompted, just exit and reboot.   
      
   d) install TCPAPPS from WARP 4 CD. Now you can configure TCP settings.   
      
   e) go back into MPTS and add NetBIOS over TCP protocol.   
      
   f) install peer networking from WARP 4 CD (IBMPEER/PEERRMT.EXE).   
      
   g) apply fixpak: TCP/IP For OS/2 V3.1 & V4.0 Universal FixPak UN_0980   
      
   h) DO NOT apply MPTS upgrade 8423/8425, it killed my outbound transfer   
   speed. 8400 is fast, leave well enough alone.   
      
   Now what you end up with is MCP2 running the older 16-bit TCP stack; you   
   could upgrade to MPTS 8610/8621 if you really want the 32-bit stack, but   
   why? The 16-bit stack is just as fast in my performance tests. You can't   
   upgrade to the TCP apps from MCP2, because that will reinstall the MPTS   
   we deleted in step b), and there goes your peer networking.   
      
   Note, TCP comes in two pieces: the TCP protocol stack is part of MPTS,   
   while the apps are a separate package. It was all very confusing until I   
   understood that.   
      
   So again, you can upgrade to the 32-bit protocol stack (MPTS 8610) if   
   you feel that you must, but beware of compatibility between the 32-bit   
   protocol stack and the old 16-bit TCP apps; see all the readme's for   
   details. And remember, do NOT install the 32-bit TCP apps from MCP2, it   
   "upgrades" MPTS to the broken version.   
      
   Have fun ...   
      
   --- PCBoard (R) v15.4/M 250 Beta   
    * Origin: Torres Vedras - Portugal (2:362/6)