[Coco] Need a dir -e but extended.

[gene heskett]

On Tuesday, December 21, 2010 04:20:19 pm Robert Gault did opine:

> gene heskett wrote:
> > Greetings;
> > 
> > I have a bad fd sector that is making dcheck bail out.
> > 
> > It is reporting a sector error for a sector that is not even on the
> > disk, so its obvious I have a contaminated FD sector, but a few hours
> > of doing dir -e's here and there looking for a bogus list, I have not
> > found it yet.
> > 
> > A decade or more back, we had a disk or file utility that worked
> > something like a dir -e does now, but where a dir -e only gets the
> > location of that filenames fd sector and reports that as the files
> > address, it read and decoded the rest of that sector to show where
> > each piece of the file was located on the disk, and also the size of
> > the file from that FD, this utility returned a complete list of all
> > the allocated sectors and the size of each allocation.  So it showed
> > the offset and size of every segment of a files fd sector.  But I
> > don't recall the name of the thing and nothing I see on that
> > Seagate's various cmds dirs (there are several) rings even a teeny
> > little bell.
> > 
> > Can someone refresh my memory?  Please?
> 
>   No idea about a special DIR command. What I normally do, is save the
> dcheck work files and compare them with the actual FAT using dEd.
> dcheck -m
> The comparison is simple if you have two windows open with dEd running
> in each. Just flip screens and the changes are easily spotted.
> 
> Usually I can find what is wrong and make repairs. If not repairs, then
> I can remove bad files or sub-directories from a good directory and the
> FAT.
> 
This is what I have done, zeroing the leading byte of any dir entries I 
know are trashed, but have not actually run  a del command because the file 
may have a bad descriptor and I'd be far worse off than before.  The idea is 
to create a clean filesystem, then let dcheck toss me a list of FAT bits to 
clear.  I have found about a dozen 3 byte strings that match the bogus FD 
sector that is killing dcheck in its tracks, but none of the ones I've 
found are located where they would need to be to make a bad FD sector 
entry.  But I'm (actually ded, the f function) still looking, haven't 
reached even 10% into the disk so far.

Even if I did find the $812710 pattern in the right location, then I'd need 
to correlate it with the correct directory entry, and os9's file structure 
does not have a link backwards to the directory entry that FD represents, 
making it quite difficult to match the directory entry up with the FD sector 
when all you have is the FD sector.

That directory like utility would be quite handy if I could locate it, 
otherwise I may have to write it.  And that would make 3 days work into 3 
weeks.  Too much rust in the Captain Armstrong secret code rings wheel 
now...

> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Lookie, lookie, here comes cookie...
		-- Stephen Sondheim