Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!im4u!ut-sally!utah-cs!utah-gr!stride!l5comp!scotty
From: scotty@l5comp.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: PD Boot Disks / Posting of PD INSTALL program
Message-ID: <146@l5comp.UUCP>
Date: Sun, 24-May-87 17:59:12 EDT
Article-I.D.: l5comp.146
Posted: Sun May 24 17:59:12 1987
Date-Received: Thu, 28-May-87 06:02:54 EDT
References: <504@myrias.UUCP> <1868@cbmvax.cbmvax.cbm.UUCP>
Reply-To: scotty@l5comp.UUCP (Scott Turner)
Organization: L5 Computing, Edmonds, WA
Lines: 29
Summary: Which is it? Offical or unoffical?

In article <1919@cbmvax.cbmvax.cbm.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes:
>First of all, let me set your mind at rest.  There really isn't a problem
>with distributing disks that have had our 'Install' program run on them.
>That was a case of people 'assuming'.  Its the files on the disk that
>is the issue here.  (so, enough install programs already!)
>
>			unofficially,
                        ^^^^^^^^^^^^
>			andy finkel
So IS this the 'offical' line on install or not?

In any case, the PD install programs don't write trash out to the disk. And as
I pointed out said trash CAN include SOURCE code or OTHER embarrasing items...
If you run a text editor alot I found that the chances of install grabbing ram
with some text editor text in it were VERY high.

The PD install programs also allow authors to make disks that come up and say
"Don't boot me silly! (RTFM)". They could of course setup the startup-sequence
to do this, but then when the disk was copied to a workbench disk it'd still
have that startup unless they supply TWO startup files... And life is tough
enough already. :)

Scott Turner


-- 
L5 Computing, the home of Merlin, Arthur, Excalibur and the CRAM.
GEnie: JST | UUCP: stride!l5comp!scotty | 12311 Maplewood Ave; Edmonds WA 98020
If Motorola had wanted us to use BPTR's they'd have built in shifts on A regs
[ BCPL? Just say *NO*! ] (I don't smoke, send flames to /dev/null)