Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!ll-xn!mit-eddie!uw-beaver!cornell!rochester!bbn!uwmcsd1!marque!gryphon!richard
From: richard@gryphon.CTS.COM (Richard Sexton)
Newsgroups: comp.sys.amiga
Subject: filesystem Q&A
Message-ID: <2186@gryphon.CTS.COM>
Date: 18 Jan 88 08:35:06 GMT
References: <2060@gryphon.CTS.COM> <3128@cbmvax.UUCP> <2137@gryphon.CTS.COM> <3151@cbmvax.UUCP>
Reply-To: richard@gryphon.CTS.COM (Richard Sexton)
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 17

In article <3151@cbmvax.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes:
>
>Most of those GURUs/Software Error requesters *are* AmigaDOS
>checking the validity of those lists, blocks, and variables
>it considers important, and giving up if it thinks things are
>too far gone.  Bringing up the Software Error requester doesn't
>halt the machine...on a 2 drive system you can even save to the
>other drive (after AmigaDOS checks that one, of course)

Ok. I have no problem with AmigaDOS determining that a disk
is to ^&#('ed up to use, but does the system really have
to corrupt itself to determine a disk is scrambled ?


-- 
            "It's too dark to put the keys in my ignition"
                        richard@gryphon.CTS.COM 
   {ihnp4!scgvaxd!cadovax, philabs!cadovax, codas!ddsw1} gryphon!richard