Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!agate!violet.berkeley.edu!pete
From: pete@violet.berkeley.edu (Pete Goodeve)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice 5.0 don't work (the way I want it to)
Summary: don't need to reboot before compiling on a small system
Keywords: setup scripts
Message-ID: <18015@agate.BERKELEY.EDU>
Date: 8 Dec 88 09:22:58 GMT
References: <866@koko.UUCP> <5021@garfield.MUN.EDU>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 34

In article <5021@garfield.MUN.EDU> john13@garfield.UUCP (John Russell) writes:
>In article <866@koko.UUCP> rayz@koko.UUCP (Ray Zarling) writes:
>>
>>Anyone know of a simple work-around for us poor people without hard disks
>>who don't want to reboot just so they can do some compiling?
>
>What you really need is about 2 megs of memory. [....(otherwise set up
>specialized work disks)....]
>
>In any case you'll need a number of CLI / Shell scripts to customize your
>setup for compiling, wordprocessing, using certain paint programs, etc. 
>

...I too, have a number of specialized system disks, but I never usually
have to reboot.  I've standardized on a command script called "use" on
all of these disks, which simply reassigns all the necessary system 
directories, paths and so on to something suitable for the task at hand.
Then I just have to type "df0:use" to get going in that environment.
[Well, until 1.3 came along, if you didn't use Sili(Con:) you would have
had to type "execute df0:use" or something...(:-))].

Now that I have lots of memory [thanks Mike -- it's still running fine!],
I keep C: itself in VD0:, and work there, and my 'use' script mainly just 
inserts the new stuff into the path, but for C compiling, for example, it also 
assigns INCLUDE: and LIB: and so on.  If you want to work entirely from
floppies, you'll have to assign DEVS:, L:, and so on as well.

Oh, yes -- in that case you want to make your first script command

	DF0:C/assign C: DF0:C

so that all the rest of the commands can be executed from the C: directory 
currently available.
					-- Pete --