Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!nic.csu.net!beach.csulb.edu!csus.edu!decwrl!sdd.hp.com!caen!hellgate.utah.edu!fcom.cc.utah.edu!npd.novell.com!newsun!saddison
From: saddison@ca.excelan.com (Skip Addison)
Newsgroups: comp.sys.novell
Subject: Re: Request for suggestions on NetWare mapping schemes
Message-ID: <1991Mar13.173901.17115@novell.com>
Date: 14 Mar 91 07:16:13 GMT
Sender: news@novell.com (
Lines: 56

The News Manager)
Nntp-Posting-Host: ca
Reply-To: saddison@ca.excelan.com (Skip Addison)
Organization: Novell, Sunnyvale, CA
References: <1991Mar12.230723.6040@uwslh.slh.wisc.edu>
Date: Wed, 13 Mar 1991 17:39:01 GMT

In article <1991Mar12.230723.6040@uwslh.slh.wisc.edu> lishka@uwslh.slh.wisc.edu (a.k.a. Chri) writes:
>... Thus, we need to
>create MAPs to the new volumes so that users can access the data on
>them. ...
>
>Our biggest problem right now is finding the best way to create maps
>to the new volumes.  
> ...

Most installations (that I'm aware of) put all or most of the application 
drive mappings either in the system login script or in centrally-administered
batch files (located in SYS:PUBLIC or SYS:BATCH, for example).  If you move
an application from SYS: to VOLA:, just change the drive mapping in that one
location.  Users home and miscellaneous directories are often set up in the
system and user login scripts.  They may need to be changed individually if 
they're in the user login scripts.

>We have several needs:
> ...
>    (e) The users do not necessarily use the same PC all of the time; i.e.
>	there is a lot of "floating" or "musical PCs" going on here.

That's why the drive mappings should be in login scripts or elsewhere on the
file server.

>    (f) We have quite a few programs that refer to directories and files
>	only through drive letters (e.g. WordPerfect).

That's why you HAVE drive mappings.

>...  However, programs like WordPerfect require that absolute
>references to directories on "drives" (or volumes) other than the
>current drive *must* be accessed through a drive letter, and will not
>work if a volume name is used ...

You WANT it to work that way.  Otherwise to change the volume for different
applications, you'd have to individually reconfigure each application, and
in some cases, each user's configuration file.

Suggestion:  

Use drive mappings to refer to the location of the application.  For example,
set it up so that WordPerfect is always on drive W:.  Map drive W: to the
appropriate volume:directory in the system login script or in a batch file
maintained by the supervisor.  That way if you later need to move WordPerfect
you just need make the change in one location.  

Having drive letters refer to specific volumes is a recipe for disaster in 
your environment where you have to move applications around.

-- Skip