09-26-1997,Jim Trulock wrote to All:
JT> Computer 2 would essentially be a "stand alone", except 
JT> that it would use the Internet utilities on Computer 1 to 
JT> reach the internet.
Making it a code server? Won't work.  What will work is that computer
2 can execute programs stored on computer 1 - but they will run on
computer 2, not 1.
JT> Both computers would run OS/2 Warp 3.0 Connect.  Computer 1 
JT> has both TCP/IP and IBMPEER, but Computer 2 only has 
JT> IBMPEER.
For #2 to run any internet access programs it will need tcp/ip
installed and configured.  Once you do that, you can either share the
comm port with the modem on #1 and let #2 treat it as a local modem. 
That's quick and dirty but it allows only 1 machine at a time to access
the modem/internet. 
JT> Is it then possible for Computer 2 to connect to Computer 1 
JT> (via the LAN), start a PPP session on Com2, and then view 
JT> web pages using Web Explorer on Computer 2?
OK, here's the alternative to just sharing the comm port with the
modem on it.  Get Injoy, register it with the mid-priced option ($35 or
so) and run it on #1.  Configure it to use ip masquerading and
Dial-on-Demand.  What you wind up with is a system that lets one or
BOTH machines use the internet connection, even at the same time.  The
machine with the modem and InJoy actually establishes the PPP
connection to your ISP but that connection is now available to any
machine on the net.  You will need tcp/ip on all machines.
I use this setup here.  Normally, it's only me and the wife but when
the kids are home from college I will have as many as 4 machines which
all have full i-net access.  This means I never hear "will you PLEASE
get off so I can get my email" even if 4 users do tend to demand more
than a 33.6 modem can do if we are all on the web at once.
JT> Also, is it possible to boot IBMPEER without the LOGIN screen
JT> coming up? Just  curious, in case of power failures.   I wouldn't
JT> require  a separate login for each member of the family, as on my 
JT> machine (Computer 1), I would only share those  dirves/directories
JT> that I choose to share. 
Do not start IBMPEER at bootup.  Instead, create a program object in
the startup folder (a copy, not a shadow) for LOGON with an appropriate
password as it's argument.  Logon requires peer, so it forces all the
necessary pieces to start before it actually logs on.
You appear to be running Warp 3 Connect.  You will need to look into a
couple of fix packs for Warp as well as some updates for the tcp/ip
stack and MPTS.  Email me at the address below if you get serious about
this and need more help.  IMO, it's well worth the effort.
Will Honea
whonea@codenet.net
--- Maximus/2 3.01
1:128/166)
---------------