From the readme file:

> ForkZapper is a utility that will erase the data and/or resource
> fork of a file. Each Mac file can have two (2) forks, a data fork
> and a resource fork. Typically applications, extensions, cdevs and
> other ?run-able? beasties contain most of their information in the
> resource fork. Documents created from those ?run-able? items usually
> contain information in the data fork.
>
> OK, But Why Would I Want To ?Zap? A Fork?
>
> Because it?s there. Well, OK, maybe some practical examples would
> help.
>
> ? It?s a fast way to erase the contents of a file, with out trashing
> the file itself.
>  ? Running a ?Fat Binary? in a 68K Mac is a waste of space. Zapping
>  the data fork take the ?Native Fat? out of the fat binary.
>  ? Millions of other potential uses that any reasonably talented
> marketing person could come up with?
>
> Now That I Have Something To ?Zap?, How Do I Do It?
>
> Simple. Double click on ForkZapper. Select Zap from the File menu.
> Navigate to the desired file. From the Pop-Up menu at the bottom of
> the dialog select which fork (or both) you wish to ?zap?. Select
> Open. Zzzzzzaaaaaappppppp! That?s all, nothing else.
>
> Really?
>
> Well, OK. There is a Drag & Drop interface from the Finder. Simply
> drag the file(s) to be zapped onto the ForkZapper icon and release.
> If no keys are held down then the data fork will be zapped. If you
> hold down the command key when you drop the file(s), the resource
> fork will be zapped. If you hold down both the command key and the
> control key while dropping, both forks will be zapped.
>
> That?s It?
>
> Pretty much. The ultra cool, wickedly wizzy ?About Box? has all the
> information on how to get ?InTouch? with me if you have problems or
> questions. ForkZapper will run under System 6.0.4 and later.
> Naturally, the drag & drop interface requires System 7 or beyond.

Compatibility
Architecture: 68k