[Prev][Next][Index][Thread]

Re: To take arms against a .SEA of troubles



EricB@pobox.com (ericb@psu.edu (Eric Bennett)) wrote:

> To the original author: How did you get the file into Executor?
> If you ever had the .sea file on a PC drive and the file had no
> other extension (.sea.hqx or .sea.bin) then most likely you've
> lost the self-extracting code (which is in the original file's
> resource fork).

It came in the mail, uuencoded as ThisFile.sea, and I uudecoded it
under Unix before looking at it in Executor.  If the self-extracting
code is supposed to live in the resource fork, then I assume that
the friend who sent it (a Mac person, but not very technically
literate) lost it in the uuencoding process.  I've already asked
her to resend it as a .hqx or .bin.uu or almost anything else, so
I think the problem will soon be solved.  Forks are evil....

``In Cyberspace, Everybody  |================================================
Can Hear You Scream.''      | Joshua W Burton  (847)677-3902  jburton@nwu.edu
 -- motto, alt.usenet.kooks |================================================


Follow-Ups: References: