Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sunybcs!bingvaxu!leah!uwmcsd1!marque!ddsw1!gryphon!richard
From: richard@gryphon.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Not a DOS disk
Message-ID: <1514@gryphon.CTS.COM>
Date: Sat, 12-Sep-87 03:18:28 EDT
Article-I.D.: gryphon.1514
Posted: Sat Sep 12 03:18:28 1987
Date-Received: Sun, 13-Sep-87 08:17:53 EDT
References: <373@io.UUCP> <2310@cbmvax.UUCP> <376@io.UUCP>
Reply-To: richard@gryphon.CTS.COM (Richard Sexton)
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 56
Keywords: Cant find a file

In article <376@io.UUCP> carlos@zapp.UUCP (Carlos Smith) writes:

>Welll, all I know is what the machine told me. I had a drawer that I attempted
>to discard with the workbench (on my hard disk, unfortunately). The operation
>failed with an "error 205, object not found". It wouldn't delete the directory
>because it wasn't empty, and the only thing listed in the directory was a file
>that it complained it couldn't find.

This happened to me too.

> I tried a simple 'C' program to unlink
>the file directly, it also failed because it couldn't find the file listed
>in the directory. The validator never seemed to be invoked, or to find it if 
>it was. I wasn't up to writing a disk editor at the time, so eventually I 
>tried diskdoctor on it (I had heard a rumor that it worked on hard disks) 
>after selectively backing up all the other directories. It just trashed the
>disk, and THAT invoked the validator. IT recommended diskdoctor, and after a
>couple of cycles of this I reformatted. Interestingly, one thing the 
>diskdoctor did was resurrect a whole bunch of files that HAD been deleted, 
>and left them at the root. Now that I have Sectorama, I would poke around 
>with that. In fact, I can't wait for it to happen again. Just let me at those
>BAMs (whats a BAM?). I'll show it... No, not really, just kidding, honest.

It happened to me on  floppy. First I noticed I have two files with the
same name. (These were files created by the Manx linker, and then copied
from ram: to df0:)

I I try to delete the offending file (On some systems I've used
you just do two deletes and no problem) and than try to delete
the remaining file. Can't do it. File not found. So I ignore
it and keep on working. Next time I write to df0: from ram:
I get a requestor saying "Disk Corrupt - Use diskdoctor".

I can't find diskdoctor.

So I reboot, and just try to get the one file off there
I care about. I insert the disk into the drive and do a cd df0:.
Ok. I type 'dir', it prints 5 filenames and puts up a "software
error" requestor, which, no matter what you do, then guru's.

Same thing happens if you try to just copy a file off the disk.

Is this friendly ?  Telling me 'bad directory - disk unusable'
would be one thing. Guruing seems a litle drastic.

Naturally, DiskSalv recovered it; Sagans of thanks, Dave,
I didnt have a recent backup. Come to think of it I didnt
have an old backup either :-)
)
>			Carlos Smith
-- 
Richard J. Sexton
INTERNET:     richard@gryphon.CTS.COM
UUCP:         {hplabs!hp-sdd, sdcsvax, ihnp4, nosc}!crash!gryphon!richard

"It's too dark to put the key in my ignition..."