Bruce LeGrande wrote in a message to HERBERT GRAF:
 BL> Thanks for the reply Herb.  This sounds promising. Although I 
 BL> don't feel comfortable using a Win based machine for a main 
 BL> server.  That job WILL fall to the 486DX4-100 OS/2 machine, but 
 BL> I'm sure that there are applications available for that OS that 
 BL> will meet (if not surpass) the WinApps.
OS/2 Warp native networking uses NetBIOS over either NetBEUI or TCP/IP.  This 
is what Microsoft calls "Windows Networking" and what IBM calls "Server 
Message Block (SMB)" networking.  In other words, OS/2 is directly 
interoperable with Windows for Workgroups, Windows 95, Windows NT, and even 
the free Microsoft Client for DOS.
There is a move to rename this protocol "Common Internet File System (CIFS)" 
and emphasize its universality and vendor independence.  For example, the 
freeware Samba package for Unix emulates an NT file and print server.
 BL> The main 'server' (as it were) will be running the main BBS
 BL> node in an OS/2 (v3.x) session 24/7, and making the inet
 BL> polls on a seperate analog modem connection (maybe even a
 BL> full time dialup, if I can swing that with a local ISP :).
There is a shareware package available for OS/2, Injoy, which provides 
front-end firewalling and IP masquerading behind a single IP address.
 BL> I'm also contemplating setting up a 'Virtual Modem'
 BL> connection on the Windows based 'surfin' machine and running
 BL> a session of Maximus (for Win3.11) as a small telnettable
 BL> BBS. This brings me to one of the main resource-sharing
 BL> subjects, of creating a 'PIPE' between this machine - the
 BL> HAM BBS - the laptop - and the main node running on the OS/2
 BL> machine, so that the users online at each system can chat
 BL> across the LAN, and the user databases and nodelists can be
 BL> shared by ALL local nodes and BBS sessions, plus it would
 BL> create a nice 'sysop presence' with access to the users from
 BL> the laptop.
You would be much better off running OS/2 Maximus and using SIO VMODEM.
 BL> The 386/33 will be running the HAM Radio BBS node (as
 BL> mentioned), so I hope that these 'microsoft client pkgs for
 BL> DOS' that you named run in the background, as the BBS mailer
 BL> needs to be in the foregrnd all of the time to answer calls,
 BL> and the OS (MSDOS 6.22) on that mach is NOT M-Tasking.
Yes, the Microsoft Client for DOS is a set of TSRs.
 BL> What is the URL for that page where I can d/l the DOS client
 BL> or even better yet an 'ftp' site URL ?
   ftp://ftp.microsoft.com/bussys/Clients/MSCLIENT/DSK3-1.EXE
   ftp://ftp.microsoft.com/bussys/Clients/MSCLIENT/DSK3-2.EXE
 
-- Mike
--- 
---------------