Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!cornell!rochester!PT.CS.CMU.EDU!cadre!pitt!cisunx!ejkst
From: ejkst@cisunx.UUCP (Eric J. Kennedy)
Newsgroups: comp.sys.amiga
Subject: Re: Planning for Shell 2.08M
Message-ID: <6841@cisunx.UUCP>
Date: 9 Feb 88 16:23:08 GMT
References: <8801221705.AA20640@decwrl.dec.com> <1698@sics.se> <8297@sunybcs.UUCP> <408@amanpt1.UUCP>
Organization: Univ. of Pittsburgh, Comp & Info Sys
Lines: 34

In article <408@amanpt1.UUCP>, mrr@amanpt1.UUCP (Mark Rinfret) writes:
> In article <6701@cisunx.UUCP>, ejkst@cisunx.UUCP (Eric J. Kennedy) writes:
> > 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
> 
> 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
> 

Yes, I saw your post after I left mine.  I can see why you're saying
it's an AmigaDOS problem, but if that's the case, why are there some
programs that handle a read/write error correctly?  i.e. stop trying to
write to the the disk and tell you it can't open the file or something.  I
wish I could give you an example of such a program, but I don't remember.
I may be remembering wrong, anyway, it's been a while since I've had a
bad disk using anything but Shell.  

Anybody else confirm or deny this?  More specifically, the question is
when you encounter a read/write error, does every program you use fail
to handle it correctly, or do some programs actually detect the error
and stop?


-- 
------------
Eric Kennedy
ejkst@cisunx.UUCP