Hi Chris.
 CH>   I am running Warp 4 at home and because of
 CH>   the limited harddrive space and some of the things that I have to do
 CH>   the laptop that work provides has Win 95 on it.  Could someone either
 CH>   point to a place where I can find step by step instructions or give me
 CH>   step by step instructions for connecting these two together?
I have Warp 4 here but its not yet installed (been too busy.....;-)), so the 
following refers to Warp 3 which should be VERY similar. 
The answer to your question depends pretty much on what you mean by 
'connecting these two together', you can use either Warp Peer services or 
TCP/IP for connectivity between the above platforms. Its my experience that 
the most useful for a local LAN environment is probably 'Peer Services' so I 
will assume that as the target. You also dont say if you have network cards 
for each machine, however I will assume that you do. 
Although it is possible to connect Peer Services using only serial ports, 
this is NOT a desirable solution for performance reasons and requires some 
extra configuration work, but it is certainly possible. Our work LAN also 
uses this method to pass NETBIOS over TCP/IP to connect LAN segments around 
the country, however our TCP/IP WAN links have plenty of resource so thats 
not a problem.
At work we have Warp machines on the same LAN as Win311, Win95 and NT 
machines, and they can all communicate with each other fine. In brief the 
steps required to set up a Warp machine are -
 - Configure the Network Adapter.
   All the above systems use NETBIOS as the basic transport, so under 
   Warp you use MPTS to configure your Network Adapter, and ensure that 
   the transport protocol 'IBM OS/2 NETBIOS' is available on that 
   adapter. You dont need to touch any of the optional settings, the    
defaults work fine.
 - Configure 'OS/2 Peer Services'.
   Again, the setup of this follows default settings, the only part to 
   watch is that each machine should have a UNIQUE network Id, so ensure
   that the 'Peer Workstation Name' box contains a unique entry.
   It also pays to align the 'Domain Name' with the same domain name
   being used by NT or Warp Server (if either of these are present on
   your LAN).
And thats about all thats needed to get the machines capable of talking to 
each other. From here, you need to decide what Users and Resources are needed 
for your environment.
Now its just a case of configuring -
 - Users and their access rights,
   This is setting up the login names and access rights that each user 
   has on THIS machine.
 - The 'Shares'.
   These are the actual resources on the Warp machine you wish to offer 
   to other workstations, and what access rights are needed to allow them
   to get access to those resources.
 - The 'Connections'.
   These are the resources that you wish to conect to on OTHER mcahines, 
   IE the 'Shares' being offered on those machines.
Under OS/2 Warp, 'UPM Services' (User Profile Management Services) handles 
the user information, and the 'Sharing and Connecting' folder handles the 
last 2 items.
I hope this at least gets you started, in most cases the task is easier than 
you think, but occasionally there are some odd quirks that you can run into. 
If you need more detailed info, then point us at the area of the question and 
just ask.
Regards..........pk.
--- Maximus/2 3.01
---------------