Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!usc!apple!motcsd!motsj1!mcdchg!ddsw1!tronsbox!bleys
From: bleys@tronsbox.UUCP (Bill Cavanaugh)
Newsgroups: comp.sys.amiga
Subject: Re: Assign & Path (Sometimes)
Message-ID: <25d21c33:4164.7comp.sys.amiga;1@tronsbox.UUCP>
Date: 9 Feb 90 03:00:30 GMT
References: <8915@nigel.udel.EDU> <182@ccave.UUCP>
Lines: 29

>When you do an EndCLI, the CLI is closed (you know that). When you close
>a CLI, all local data is lost (the path is local data, you didn't knew
>that, did you?).
>
>So add "Execute S:WPAssigns" to your S:Startup-Shell (if you have one,
>create it otherwise), this should solve your problem.

I've got my paths added rather early in my Startup-Sequence.  After all the
assigns, etc. are done (did you ever notice how many more assigns you have
when you have a hard drive?<grin>), I run VirusX, LoadWB, and then open a
WShell 1.2.  I should have said this takes place in the StartupII file, BTW.
 The last thing that happens is the original startup-sequence closes the
boot CLI.
  My paths are inherited by all subsequently opened WShells.

Including a script to create paths in you wshell-startup will REALLY make
the system slooooow, IMHO.  But I'm impatient;  my wshell-startup and config
files are in ENV: in RAM...<grin>

     /************************************************************
     *                                                           *
     * Everything above is copyright me.  All rights unreserved. *
     * uunet!tronsbox!bleys         BIX: bcavanaugh              *
     *                                                           *
     * "The perversity of the universe tends to a maximum"       *
     *                              Finagle's First Law          *
     *                                 J. Pournelle              *
     *                                                           *     
     ************************************************************/