Path: utzoo!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!ubc-cs!uw-beaver!cornell!llenroc!batcomputer!rpi!usc!cs.utexas.edu!ut-emx!boerner
From: boerner@ut-emx.uucp (Brendan B. Boerner)
Newsgroups: comp.sys.novell
Subject: Re: Novell volume-related problems
Message-ID: <45571@ut-emx.uucp>
Date: 14 Mar 91 04:46:12 GMT
References: <1991Mar12.230827.6139@uwslh.slh.wisc.edu>
Organization: UT Austin
Lines: 20

In article <1991Mar12.230827.6139@uwslh.slh.wisc.edu> lishka@uwslh.slh.wisc.edu (a.k.a. Chri) writes:
[...]
>Another problem we have had with volumes and mapping is that if we are
>connected to another server by accident and we use this other server's
>LOGIN.EXE to login into our server (i.e. LOGIN MYSERVER/MYLOGIN), the
>other LOGIN.EXE seems to "eat" the first directory off of the PC's
>path.  This continues to happen until all of the directories in the
>path disappear after repeated LOGINs.  It is very annoying!  The other
>server is also running 2.15c, although the LOGIN.EXE on that server is
>older than the LOGIN.EXE on our server.  Is this a known bug?

If you use MAP S1:=whatever instead of MAP INS S1:=whatever, MAP
will eat the path as you describe.  Other than that, I'm not familiar
with bugs in LOGIN.EXE which will do as you describe.  For starters,
I'd make sure that all of your servers have the latest LOGIN.EXE.
A particularily nasty problem to debug will crop up if you have a
LOGIN.EXE which does not support MAP ROOT and you use MAP ROOT in
your login scripts and inadvertently use the old LOGIN.EXE.

Brendan