Path: utzoo!utgpu!water!watmath!clyde!att!mtunx!rutgers!cmcl2!nrl-cmf!ames!pasteur!agate!eos!aurora!wiedmann
From: wiedmann@aurora.uucp (Christian Wiedmann)
Newsgroups: comp.sys.mac
Subject: Re: MacZap's about as useful as a crashed hard disk
Message-ID: <856@eos.UUCP>
Date: 9 Jun 88 01:53:50 GMT
References: <107@mace.cc.purdue.edu> <2734@utastro.UUCP> <108@mace.cc.purdue.edu>
Sender: news@eos.UUCP
Reply-To: wiedmann@aurora.UUCP (Christian Wiedmann)
Organization: myself
Lines: 26

After seeing all these comments about MacZap, I've decided I need to put
in my two cents worth. 
MacZap looks like a great program, but seems unfinished.
For example, why can't you recover a floppy with just one disk drive? Here's
what happened when I tried:
I've got a bad floppy. I boot a disk with MacZap recover on it, and run the
program. I pop in the bad disk. MacZap says it needs to read a parameter file.
Fine, I insert the disk with parameter files, and then choose the apropriate
file ("800K Floppy", or something). It then reads the file, and starts
recovering files. Unfortunately, it never ejects the floppy to let me insert
the bad disk.
Is there any way to do this correctly? I tried putting the parameter files
on a 400K disk and using the external drive I have. This worked to a certain
extent: MacZap found all the files and folders on the disk. But when I tried
to recover those files, it flashed a message for about half a second and then
stopped. (The message said "Error during recovery". Why was there no delay
so normal humans could read it?) I finally gave up.
It can't be very hard to fix this problem. I don't even care if I have to
swap disks a zillion times, just as long as I can do this. What MacZap needs
is cleaning up.
	-Christian

net address: wiedmann@aurora.arc.nasa.gov
UUCP: {ihnp4,ucbvax,nike,lll-crg}!ames!aurora!wiedmann
disclaimer: Any resemblance of this opinion to anybody else's is purely co-
incidental.