Path: utzoo!utgpu!water!watmath!clyde!bellcore!decvax!decwrl!sun!pitstop!sundc!seismo!uunet!nuchat!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Disk Errors. AmigaDOS file system.
Summary: You're still looking at my finger.
Message-ID: <1403@sugar.UUCP>
Date: 16 Jan 88 07:29:26 GMT
References: <1338@sugar.UUCP> <3080@cbmvax.UUCP> <1368@sugar.UUCP> <3117@cbmvax.UUCP>
Organization: Sugar Land UNIX - Houston, TX
Lines: 46

Once upon a time an Amiga Guru was approached by a Zen master, who was
having a problem with AmigaDOS. The Guru suggested the Zen master show
him the problem, so they went into the Guru's office. The Guru went out
to get a cup of coffee while the Zen master played with the Guru's high
zoot Amiga. When the Guru came back the Zen master waved the pointer
(which was shaped like a mouse) over a window, saying "what's this?"
The Guru said "Oh, that's just my pointer". The Zen master hit him over
the head with a copy of the ROM Kernel Manual and turned off the Amiga.

In article <3117@cbmvax.UUCP>, schein@cbmvax.UUCP (Dan Schein CATS) writes:
> In article <1368@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
> >OK. Let's get this straight. I wasn't flaming Manx, I was flaming you.

OK. Let's get this straight...

> >
> >The problem is with disk errors.

>   I think you could have been just a bit clearer on your original posting. 
>   I very seldom ever use floppies for anything but storage. I use VDK: (RRD)
>   to do my work in, that may be why I never noticed the problems your having.

Before I hit you over the head with a copy of the ROM Kernel manual, would
you like to explain why that's relevent?

I just used the example of 'Z' because it was the particular instance where
I ran into the problem. It could happen anywhere, and it's equally annoying
wherever it happens. You can cut things down by not writing to floppies that
often, but the problem remains. Eventually it's going to bite you.

The problem is that (1) the Amiga is very susceptible to disk errors, and (2)
that the file system should NOT abort writing a file just because it gets
a disk error. (1) can be solved by going to a more robust file system (like
having real sectors on the tracks). (2) can be solved by trying to rewrite
the offending block on a new track. Then, at least, the file could be
saved.

I'd MUCH rather have the file system AND the device driver try to recover
than neither doing so, which is where I am now.

Now, does the Amiga have buddha-nature?

PS: Apologies to the author of "AI Koans". It just seemed so appropriate.
-- 
-- Peter da Silva  `-_-'  ...!hoptoad!academ!uhnix1!sugar!peter
-- Disclaimer: These U aren't mere opinions... these are *values*.