Path: utzoo!mnetor!uunet!cbmvax!steveb
From: steveb@cbmvax.UUCP (Steve Beats)
Newsgroups: comp.sys.amiga
Subject: Re: Planning for Shell 2.08M
Message-ID: <3286@cbmvax.UUCP>
Date: 9 Feb 88 13:51:33 GMT
References: <8801221705.AA20640@decwrl.dec.com> <1698@sics.se> <8297@sunybcs.UUCP> <6701@cisunx.UUCP> <408@amanpt1.UUCP>
Reply-To: steveb@cbmvax.UUCP (Steve Beats)
Organization: Commodore Technology, West Chester, PA
Lines: 27

In article <408@amanpt1.UUCP> mrr@amanpt1.UUCP (Mark Rinfret) writes:
>In article <6701@cisunx.UUCP>, ejkst@cisunx.UUCP (Eric J. Kennedy) writes:
>> 
>> Here's what I would like to see in Shell 2.08M:  I would like it to
>> respond correctly to 'volume xxx has a read/write error' requesters.
>> When I'm copying a file to a disk and encounter an error, I can hit
>> cancel all day, and do nothing but wear my drive out.  If I take the
>> disk out, I get 'you MUST replace volume xxx in drive n!!!'  
>> ...
>
>Eric - you're describing the same symptoms that I have encountered.  I recently
>posted an article with a short program that demonstrates this (and runs stand-
>alone).  I believe the problem to be in AmigaDOS and not the Shell.
>
>> Eric Kennedy
>> ejkst@cisunx.UUCP
>
>Mark
>

I haven't been following this thread, but this article caught my eye.  I think
the problem is in AMigaDOS and is related to the dreaded 3 second timeout.
DOS is trying to write the bitmap back to disk because it has been altered but
the blocks allocated for the bitmap are bad.  Since the FS doesn't take this
possibility into consideration, it constantly loops.  Fixed in FFS.

	Steve