SC> I now have 3 different computers running 3 different os's.  I have 
specific
  > uses for each & need to connect them all.  The main machine runs OS/2.  
The
  > Win95 machine is important & the dos box could go away.
SC> What is the best way to connect these boxes?  The OS/2 & win95 boxes are 
in
  > different rooms but running cable is not a problem.  The dos box is next 
to the
  > OS/2 box.
SC> All I need is a communication link between the 2 boxes.  I would like to 
be
  > able to access my BBS from the Win95 & dos boxes.
   You can run the MS network client on the DOS box, then all three 
   boxes will be able to see each other.
   Here's how:
   Download the following files from MS:
   ftp.microsoft.com in /bussys/clients/msclient - Files are: 
   DSK3-1.EXE and DSK3-2.EXE
   You also need to get the newer NET.EXE file from 
   /softlib/mslfiles - File is: WG1049.EXE (Adds server capability)
   You will need a network card that includes an NDIS 2.0 or greater 
   driver. (Most all do...). Don't expect a bus-mastering driver to 
   work without some pain. (I could NOT get a Kingston PCI 100mbs 
   card to work with QEMM at all, had to go back to an ISA card).
   Install the first two disks and get it working as a client. Then 
   overwrite your original NET.EXE file with the above version, and 
   you will have server capability.
   Suggest you change the default values for "Sessions" and "NCBs" 
   in PROTOCOL.INI to at least 16 and 32 respectively. The default 
   values are insufficient.
   Using QEMM and the Helix mouse driver and disk cache, and running 
   QEMM's VIDRAM, I get about 609k free for my DOS BBS to run in, 
   and that's WITH a 8 meg ram disk, and FAX and Stomper modem 
   sharing TSR's installed. Works like a champ, but it gets a bit 
   unstable when a BBS caller does a Doorway shell and pokes around 
   the network. 
                                       LRA
 -- SPEED 2.00 #2720: Finally picking up on subtleties huh?
--- Platinum Xpress/Win/Wildcat5! v2.0
---------------