🚀 go-pugleaf

Seems I spoke way too soon about giffer. Here's what happened:
I dropped the parts on my UNIX box, edited out the commentary,
and ran it through xbin. xbin claims no errors, and I get
out the .info, .data, and .rsrc parts as expected... When I upload
this file to the macintosh, using macput and Macterminal 1.1
file transfer, the upload happens with no errors. Unfortunately,
the Mac II believes that this is a MacWrite file, not a .pit file.

Does anyone have any gueses as to why this might be and what I can
do about it? I plan to try:

	Uploading the hex and going through BinHex4.0 if I
		can find it
	Rebuilding the desktop.

The sad thing is that the silly program looks legitemate, but
further examination reveals that the resource fork is empty,
and the data fork has the only valid data. Is this a Macterminal
bug? Does MacTerminal assume that a file with no resource fork
is a text file?

	I will also try to simply *set* the file owner and type
	to what I know they should be.

Any and all help would be appreciated. I really want to take a
look at this stuff. Has *anyone* gotten this to download correctly?

Jon Shapiro
AT&T Information Systems
Summit, N.J.