Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!sun-barr!lll-winken!aunro!alberta!herald.usask.ca!weyr!f43.n140.z1.FIDONET.ORG!lowey
From: lowey@f43.n140.z1.FIDONET.ORG (Kevin Lowey)
Newsgroups: comp.dcom.lans
Subject: Re: LAN MANAGER Questions.
Message-ID: <267.284889FE@weyr.FIDONET.ORG>
Date: 31 May 91 21:53:25 GMT
Sender: ufgate@weyr.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:140/43 - U of S Computing Se, Saskatoon Sask
Lines: 30


 AM> I guess it depends on what you expect out of a LAN.  Things like PCSA and
 AM> PCNFS are designed to provide connectivity from you PC to some non-PC (ie
 AM> mini or above) computer (ie PCNFS to UNIX host/servers and PCSA to VMS
 AM> host/servers)
 AM> 
 AM> I see a LAN as something that provides PC-PC connectivity, as well as
 AM> PC-(big machine) connectivity.  I guess my ideals are approaching a
 AM> distributed network (everyone can access everything).

PCSA provides PC to PC connectivity as well.  For example, you can leave a 
program running on your PC which will allow other programs to copy files
to and from it.  Thats under the MS-DOS version.

I use the OS/2 version.  Pathworks under OS/2 provides full 
interconnectivity.  I can run my PC as a server, a client, or both at the 
same time.  It is a full MS Lan Manager compatible implementation.

However, I see your point.  It would be nice to have something like what is 
in the Macintosh system 7 software.  It allows EVERY machine to be both a 
client and a server for any other machine on the Appletalk network.  That 
support is built right into the operating system.

- Kevin Lowey


--  
Kevin Lowey - via Benden Weyr - FidoNet Node 1:140/22
    Internet: lowey@sask.usask.ca
    Standard Disclaimers Apply...