Subj : Re: sound
To   : Bonno Bloksma
From : Darren Gibbs
Date : Thu Dec 07 2000 09:53 pm

 DG>> I've _never_ put in a login script without an "exit" command at
 DG>> the end of it.

 BB> Ok, but then a user LS was impossible, while sometimes one was needed.

Never used a user login script either. :-)

 DG>> The default login script sucks anyway. :)

 BB> But what would we do without it. At some time after installing the
 BB> server one needs to startup the SysCon program on the SYS volume.
 BB> Without a default LS that creates the mapping to the SYS volume and to
 BB> the Public directory how would we ever get there?

 BB> Or..... wasn't the map command also in de Login directory....?

Actually, the map command at that point is processed by the program LOGIN.EXE - 
there's no need to be able to get to the public directory. Until the end of 
your login script processing {or encountering the EXIT command}, all the 
comands in the login script are processed by login.exe - except those directly 
referenced by putting something like

#sys:public\some_program.exe

That's the main reason login.exe is so large - it contains the code from all 
the basic commands needed to be run by the login process.

DaZZa

--- GoldED/2 3.00.Beta5+
 * Origin: WOW BBS - Coming Soon! Netware for the Nintendo! (3:712/888)

.