Re: How do I delete file comments?

[bazyar@teal.csn.org (Jawaid Bazyar)]

gdesroch@slate.mines.colorado.edu (DESROCHERS GARY FREDERIC) writes:

>grover@emunix.emich.edu (Grover Thomas) writes:
>: While using the Finder (under System 6.0) to look at Icon Info for a Shrinkit
>: archive (NuFX), I accidently pressed the "Add Comment" feature.
>: 
>: Now when I use ProTERM 3.0 to try and send the file, it gives me a nice
>: little note: "File Error - $4B"  which means unsupported file type. I
>: realize that ProTERM is a ProDOS program, but Shrinkit was able to
>: use the same file without a problem.

>     I would say that you made you file into an extended file.  That is
>what it looks like.  That is why any ProDOS 8 program cannot touch it.
>But!  I do not understand why 8 bit Shrinkit would see it.  If you are
>talking about GSHK then that would be understandable.  

>: 
>: The_Big_Question:  So how do I delete the Finder Comment?
>: 

>     You can delete a finder comment?  Good questions.
>Sorry I cannot help you with The_Big_Question.

>: So far, Copy II+ chokes on it and ResLin 0.25 won't touch it.  I have
>: been able to reconstruct the file by Unshrinking it and then repacking
>: it again, but this is a large pain in the butt and can take awhile.
>: Also, I am concerned about the next file, especially if it's not a simple
>: Shrinkir archive.  How do I delete Finder Comments?

>     Personally I would expect any 8 bit program (At least as of today that
>I know of) to touch it even Copy II+.  No idea why Reslin won't touch it
>though.

  There was a IIgs program out there somewhere that stripped resource
forks off of files.  At any rate, writing one of these wouldn't be
difficult.

  Since Gary likes to do these kinds of things (right!) there are
two possibilities:
  SetEOF(0) on the resource fork.
  Copy the data fork to a new file, delete the old one, rename the new
   one to be the same as the original.

  In one of these cases (the second for sure, hopefully the first as well),
you now have a file without a resource fork.

  Trouble is, once a resource fork is added to a file, I don't think SetEOF(0)
will _completely_ get rid of it; the 'extended' markings are probably
all over the directory entry.  So do the second and be safe.

-- 
 Jawaid Bazyar              |   Ask me about the GNO Multitasking Environment
 Procyon, Inc.              |   for the Apple IIgs!   
 bazyar@cs.uiuc.edu         |   P.O Box 620334
 --Apple II Forever!--      |   Littleton, CO 80162-0334   (303) 933-4649