Re: Help! Filetype $00 problems . . .

[Randy Shackelford <shack@onyx.southwind.net>]

Rubywand <rubywand@swbell.net> wrote:

:      It looks like, as Randy explains, the simple BLOAD ... T$00 ... fix is
: out. The resource forks are a real pain. 

:      If you have Block Warden or Copy II+ (ProDOS) it is not all that hard to
: manually rip off the resource fork and change filetype of ProDOS files on
: your IIgs. (It's somewhat easier using a good block editor, like Block
: Warden). 

You need to know the file system awfully well to do this without ending up
with a munged volume for your trouble. Once upon a time I wrote a program
that reads the data fork of an extended file and writes the data to a
normal file. I tried to write a program to delete extended files, but I
never got it to fix the volume correctly. The BLOCKS_USED count was always
off.

:      Basically, you use information saved in a file's 'fake' key block to
: modify the file's directory entry so that it becomes a file of the correct
: type which no longer has a resource fork. (And, once you get ProSel going,
: you can de-allocate the blocks freed up by dumping the resource.)  No doubt,
: this is what the Mac utility recommended by Randy does. 

I expect there are easier ways to manipulate file forks under Mac OS as there
is with GS/OS. You have to resort to block access with ProDOS 8. The trick
I used was creating a file entry with the storage type of one of the forks, 
then changing the entry's link to point to the fork. Then a delete call did 
the hard part for me. I could get rid of both forks and the extended key block
but couldn't figure out why the blocks in use was off by one. It's easier to
delete the files with someone else's software I guess.
-- 
Offsite mail to this host gets nuked.