Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!uw-beaver!ubc-cs!van-bc!rsoft!mindlink!a48
From: Ullrich_Fischer@mindlink.UUCP (Ullrich Fischer)
Newsgroups: comp.sys.novell
Subject: Mapping
Message-ID: <5215@mindlink.UUCP>
Date: 21 Mar 91 02:10:57 GMT
Organization: MIND LINK! - British Columbia, Canada
Lines: 29

Here's a possible solution to those who have been wrestling with MAP INS
problems of late:

In my system login script, I map drive letters as needed according to the
users' group membership.  I map no search drives, but (again determined by each
user's group membership) use the DOS SET PATH= command in the login script to
set the DOS PATH.  This seems to work on our 286 servers as well as the 386
server.  The only wrinkle here is that where in dos you might use
PATH=C:\DOS;C:\NORTON;D:\fox210;...
the corresponding DOS SET login script command has to be
 DOS SET PATH="C:\\DOS;F:\\PUBLIC;...."
since single \ characters seem to get lost.

One note on the search mapping.  You should use a minimum search path
when running under NETWARE 286 or you will run out of DYNAMIC RAM 1
(watch for it of your FCONSOLE STATISTICS SUMMARY screen) and
thereafter no one will be able to log on at best and at worst, the
server will crash.

Rather than try to include a PATH entry for every application you are
ever likely to use, set up either a menu system which moves to the
necessary directory and does temporary mapping required before calling
up each application, or set up short batch files which do the same
thing and are all located in F:\PUBLIC (which should always be in your
minimum search path).
--

---    Ullrich Fischer  phone (604) 684 9371  Vancouver, BC, Canada --- 
                 Ullrich_Fischer@mindlink.uucp