Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!think!bloom-beacon!mit-eddie!rutgers!iuvax!pur-ee!j.cc.purdue.edu!i.cc.purdue.edu!h.cc.purdue.edu!s.cc.purdue.edu!ain
From: ain@s.cc.purdue.edu (Patrick White)
Newsgroups: comp.sys.amiga
Subject: Re: Some ideas for KS/WB 1.3
Message-ID: <2075@s.cc.purdue.edu>
Date: 29 Jan 88 14:01:10 GMT
References: <8801251900.AA00551@cory.Berkeley.EDU> <2512@swan.ulowell.edu> <2293@gryphon.CTS.COM>
Reply-To: ain@s.cc.purdue.edu.UUCP (Patrick White)
Organization: PUCC Land, USA
Lines: 38
Keywords: Keywords??  Whazzat??

In article <2293@gryphon.CTS.COM> jdm@gryphon.CTS.COM (John Mesiavech) writes:
>     Include an AUTOFORMAT flag in the OS.  When this flag is set to 1,
>have the system automatically format the disk, if the Disk-Validator marks
>the disk as BAD.

   Puleeese no... the first time I pop a toasted disk into my drive (say
from some other computer, or just fails validataion) the data would go away.
   If that ever happens, I will find whoever got C=A to put that idea in and
I *won't* buy them a beer :-)

   I agree, however, it would be nice to have some basic program (say
workbench) automatically ask if I want a "bad" disk formatted when I pop
it in the drive... but there also has to be a way to shut that feature
off if I have a program that wants to experiment with it's own data
encoding format.

   
>     Related ideas:  An EXPERT gadget in Preferences, that if it was clicked
>ON, would cause the system to never come up in Workbench, always in CLI.

   If one wants CLI, they might as well learn CLI commands -- I could see
this idea causing major confusion the first time a novice click it on to
see what would happen then reboots.  Now workbench dosen't come up, and
they can't get to preferences the way they did before... now they are really
lost... 

>Anyway, just some ideas, dust in the wind...Thought I'd toss 'em out, and
>see if anyone sneezed....8->

   Achoo. :-)

   Seriously though, some good ideas, but isn't the idea of making a computer
for a novice to make it so "dumb" actions don't cause damage? (ie. to limit
the the abilities of a machine to "safe" ones?)


-- Pat White
UUCP: k.cc.purdue.edu!ain  BITNET: PATWHITE@PURCCVM   PHONE: (317) 743-8421
U.S.  Mail:  320 Brown St. apt. 406,    West Lafayette, IN 47906