Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!pyramid!voder!kontron!cramer
From: cramer@kontron.UUCP
Newsgroups: net.micro.pc
Subject: Re: Bug With PC-DOS 3.1 DEL command?
Message-ID: <802@kontron.UUCP>
Date: Tue, 20-May-86 13:44:59 EDT
Article-I.D.: kontron.802
Posted: Tue May 20 13:44:59 1986
Date-Received: Fri, 23-May-86 08:03:09 EDT
References: <785@kontron.UUCP> <787@kontron.UUCP> <1790@gitpyr.UUCP>
Distribution: net
Organization: Kontron Electronics, Mt. View, CA
Lines: 27

> In article <787@kontron.UUCP>, cramer@kontron.UUCP (Clayton Cramer) writes:
> > > We've found what looks like a severe bug with the PC-DOS 3.1 DEL command --
> > > watch out!
> > > 
> > > One of the engineers working for me typed:
> > > 
> > > 	DEL A.O
> > >         
> > > and was asked "Are you sure (Y/N)?"
> > > 
> > > Not being thoroughly familiar with PC-DOS, he didn't realize that this
> > > prompt is put out when you say "DEL *.*", so he said "y<return>" and
> > > the entire directory was cleared out.  A little experiementation found
> > > that DEL followed by ANY single filename caused it to assume that we had
> > > typed "DEL *.*".
> > > 
> > 
> > But DEL doesn't fail everytime.  Some quirk, perhaps, of the particular 
> > order of files in the directory?
> > 
> Or perhaps the directory itself is messed-up.  I would like to know if
> this can be repeated after using CHKDISK.

CHKDSK ran without complaint -- I can't make DEL fail anymore.  (Cringe!
I get real nervous about problems like this.)

Clayton E. Cramer