Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!coplex!dean
From: dean@coplex.UUCP (Dean Brooks)
Newsgroups: comp.sys.amiga
Subject: DO NOT USE DIR-WORK 1.12 POSTED TO COMP.BINARIES.AMIGA
Message-ID: <199@coplex.UUCP>
Date: 13 Oct 90 04:06:34 GMT
Organization: Copper Electronics Inc.; Louisville, Ky
Lines: 38


   I wanted to catch your eye with the subject line of this message
because I thought this was important enough to post about.

   It seems there may be an inherent flaw with the recently posted program
Dir-Work 1.12 that appeared recently in comp.binaries.amiga.  It took
only 10 seconds of using the program before it totally trashed my
hard drive.

   I had selected a directory from the selection list presented by
Dir-Work and chose the "move" gadget to move it.  At that point, I didn't
want to proceed so I exited the program gracefully (by clicking the
close requester).

   Unfortunately, Dir-Work had already moved the directory link into
oblivion and I didnt realize it until it was much too late.  I tried to
patch things up with a block editor to no avail.

   I dont know if this is a bug or an inherent design flaw, but if it
is part of the programs design to have a state where a directory is in
limbo while waiting for a user response, it a bad choice on the authors
part.  If any file linking/unlinking is to be done, it should be done
in one fell swoop, and NOT in bits and pieces.  Most certainly things
should be done to restore conditions to a sane state if program
termination is requested.

   I wouldnt have posted anything, but I felt that 10 seconds to completely
wipe out an 80meg hard drive deserves attention...  Thanks...

   ( I know, I should have been more careful with a program I had never
     used before, but hey, I assumed it had been tested thoroughly.  Of
     course we know what happens when you assume (-; )

--
dean@coplex.UUCP   Dean A. Brooks
                   Copper Electronics, Inc.
                   Louisville, Ky
UUCP: !uunet!coplex!dean