Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!husc6!panda!genrad!decvax!wanginst!ulowell!page
From: page@ulowell.UUCP (Bob Page)
Newsgroups: net.micro.amiga
Subject: Re: FASTDIR (not a substitute, but a supplement for AmigaDOS 'DIR')
Message-ID: <335@ulowell.UUCP>
Date: Thu, 15-May-86 01:04:34 EDT
Article-I.D.: ulowell.335
Posted: Thu May 15 01:04:34 1986
Date-Received: Fri, 16-May-86 05:41:18 EDT
References: <13147@ucla-cs.ARPA> <1146@amiga.amiga.UUCP>
Reply-To: page@ulowell.UUCP (Bob Page)
Distribution: net
Organization: University of Lowell
Lines: 28
Keywords: FASTDIR

In article <1146@amiga.amiga.UUCP> Robert A. Peck writes:
>Followup-To: Questions re slow DIR command
Nope.  The Followup-To: line is the newgroups to follow up to (what you
get when you type 'F'.)  You usually leave it blank except when you
want further discussion redirected to a certain newsgroup.  You might
want to put further summary lines in a field called Summary:

>I've posted to net.sources a shar archive for FASTDIR.

This appears on the programmer's toolkit disk from C-A.  I tried it,
and have some comments:
   I don't see how it is any faster than dir!
   I'm glad it doesn't print the dirs seperately.
   It should DELETE the .dir file after it is done!
   *******
   Under V1.2, if the disk fills while writing the .dir file, you
have just hung your CLI process.  FASTDIR doesn't know that the
disk is full, and retries its write.  Of course, you get another
"Volume foo is full" requester, and the cycle starts again.
I didn't try this under V1.1.

    Thanks for the directory read code, though.

..Bob
-- 
UUCP: wanginst!ulowell!page	Bob Page
ARPA: page@ulowell.CSNET 	U of Lowell CS Dept
VOX:  +1 617 452 5000 x2233	Lowell MA 01854 USA