Path: utzoo!attcan!uunet!husc6!bloom-beacon!oberon!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga
Subject: Re: FULLY INTERACTIVE SCRIPTS (A Tutorial)
Message-ID: <9084@oberon.USC.EDU>
Date: 14 May 88 17:00:17 GMT
References: <8922@oberon.USC.EDU> <9927@agate.BERKELEY.EDU> <9066@oberon.USC.EDU> <13328@tut.cis.ohio-state.edu>
Sender: news@oberon.USC.EDU
Reply-To: papa@pollux.usc.edu (Marco Papa)
Organization: Felsina Software, Los Angeles, CA
Lines: 48

In article <13328@tut.cis.ohio-state.edu| erd@tut.cis.ohio-state.edu (Ethan R. Dicks) writes:
|In article <9066@oberon.USC.EDU| papa@pollux.usc.edu (Marco Papa) writes:
||In article <9927@agate.BERKELEY.EDU| pete@violet.berkeley.edu.UUCP (Pete Goodeve) writes:
|||BTW, for my own scripts at least, I find that the sort of place where pipes
|||can be very useful (rather than writing the input line to RAM:).  Of course
|||you DO have to have pipes installed first!  Which makes the idea not so
||
||I thought about that, but had to find a place that IN EVERY case would be
||available to store the temporary files.  T: is not good since it might not
||be there.  PIPE: would be good in 1.3, except that it MUST be mounted to be
||usable, and I cannot assume that. It turns out that RAM: is always available
||and if it isn't, it will be MADE.
||
|RAM: is _almost_ always available; at least all Amigas come equipped to sue
|and create RAM:.  I disovered meny moons ago, when I first began customizing
|my workbench disks that the files in L: _were_ important.  My point is that
|while RAM: will be created if it can be, due to the actions of the user, may
|not be.
 ^^^
My script will ASSUME that it is installed on an Amiga with at least 512K,
and booted with Workbench.  I would say that will cover 99% of the current 
Amigas (Who has an A1000 with 256K?).  In that case RAM: will be "made" and
will have sufficient space for my executanles and the temp files.  If they guy
multitasks and runs out of RAM: space during installation, he will get an error
and will have to do it again.  It happened to me when installing the A2090
software with an A2000 with 512K (I had disconnected my ASDB 8MI).

|How hard is it to get an AmigaDOS redistribution license ($$$)?  If
|you can provide bootable disks to do installation, the solution becomes
|easier: mount PIPE:, use XIcon (or IconX ;-)  Just use the bootable disk to
|configure the users WorkBench disk/Application disk, or better yet... use 
|the bootable disk to format a blank disk and force the user to make a working
|copy, which is appropriately customized.

The distribution license is not the point.  PIPE: requires the PIPE: entry to
be on the Mountlist, otherwise mount PIPE: will fail.  I cannot assume that
the user will have it, and changing a MountList MUST be done with an EDITOR.
That's TOO MUCH WORK for the "average" user. The point is that the installation
MUST be run from workbench, with click and answering questions ONLY.
Otherwise it is TOO COMPLEX.  Second point, as of today few people have
PIPE: and that may be for some more considering that 1.3 is not out yet.
I guess I have to manage with what I have TODAY.

-- Marco Papa 'Doc'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
uucp:...!pollux!papa       BIX:papa       ARPAnet:pollux!papa@oberon.usc.edu
 "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=