From: brian@SJF.Novell.COM (Brian Meek)
Subject: Re: LWP files required on local PC
Organization: Novell, Inc.
Date: Tue, 22 Dec 1992 15:52:48 GMT

In article <1992Dec22.064714.11917@trantor.dso.gov.sg> kkimchio@trantor.dso.gov.sg (Kwa Kim Chiong) writes:
>Newsgroups: bit.listserv.novell
>Path: newsun!sgiblab!spool.mu.edu!yale.edu!jvnc.net!newsserver.technet.sg!iti.gov.sg!dso.gov.sg!kkimchio
>From: kkimchio@trantor.dso.gov.sg (Kwa Kim Chiong)
>Subject: LWP files required on local PC
>Message-ID: <1992Dec22.064714.11917@trantor.dso.gov.sg>
>Organization: DSO
>X-Newsreader: TIN [version 1.1 PL6]
>Date: Tue, 22 Dec 1992 06:47:14 GMT
>Lines: 5
>When I installed Lan Work Place on my local PC, it created a few
>subdirectories under c:\xln\...(software, odi, etc.), but I only need lsl,
>ge16dod, ipxodi, tcpip and telapi in my autoexec.bat. How can I set up LWP
>files on the server and keep minimum no. of files on my PC? Do I need the
>other files on my PCs?

LWP v4.0x pretty much requires that all of the files except those in
\XLN\BIN40 be left on the local drive, or in a personal directory on the 
server that is located via the "EXCELAN" environment variable and the 
"Product Root" directory defined in LWP.INI.  The files in \XLN\BIN40 can 
be anywhere in your search path.  For more particulars... check out 
sjf-lwp.sjf.novell.com: ~\lwp4dos\lwprpl.txt.

LWP v4.1 and LAN WorkGroup are much more flexible in this respect.  Here, 
the "EXCELAN" environment variable and Product Root entry in LWP.INI are 
no longer needed (except to support applications compiled with the v4.0x 
libraries).  Instead, the location of various files are maintained in 
NET.CFG under the "Protocol TCPIP" section:

	Protocol TCPIP
		path tcp_cfg	h:\net\tcp;f:\etc
		path lwp_cfg	h:\net\hstacc;f:\net\hstacc
		path profile	h:\net\profile;f:\net\profile
		path script	h:\net\script;f:\net\script

Here, all of these NET.CFG declarations define multidirectory search 
paths.  Assume that H: is mapped to the user's home directory on a server, 
and that F: is mapped to volume SYS: on a server.  In the case of IP name 
resolution, the user's personal hosts file in H:\NET\TCP will be searched, 
followed by the server's shared hosts file in SYS:\ETC.  Actually, a
RESOLV.CFG containing a list of DNS servers in one of those directories 
would cause a DNS query to occur before the hosts files are searched.

In the case of the LAN WorkPlace applications, all of the default settings 
and programs are stored under F:\NET where users have only read and filescan 
privileges.  H:\NET originally contains only empty subdirectories.  When 
Joe_user decides to change the default colors for TNVT220 to magenta text 
on a green background, the modified parameter settings are stored in 
H:\NET\HSTACC where they will be found prior to the unmodified defaults 
still located in F:\NET\HSTACC (and not everyone in the workgroup need 
become nauseous looking at magenta letters on a green background :-).

So, an upgrade to v4.1 is recommended.

-- brian
___________________________________________________________________________
Brian Meek                      Novell, Inc. -- Desktop Systems Group
                                Internet mail:  brian@Novell.COM
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU