Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!violet.berkeley.edu!steve
From: steve@violet.berkeley.edu (Steve Goldfield)
Newsgroups: comp.sys.mac
Subject: Re: Binhex - Making downloaded file executable
Message-ID: <26634@agate.BERKELEY.EDU>
Date: 25 Jul 89 14:58:18 GMT
References: <7146@leadsv.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 30

In article <7146@leadsv.UUCP> cberg@leadsv.LEADS.LMSC.COM.UUCP (Charles R Berg) writes:
#>Here's another question from a novice user.  (In the beginning, everyone was
#>a novice, weren't they?)
#>
#>No, that wasn't my question.
#>
#>I find this great file, MacCompress in comp.binaries.mac.  So, I save it into
#>a file on my Sun, edit out the header info, use Kermit to transfer it to my
#>Mac, and run BinHex to convert from download to application.
#>
#>But, what I have now is a 'document' that when I attempt to execute, produces
#>the old standard message about not finding the application necessary to open
#>it.
#>
#>Now comes THE QUESTION. What step am I missing and/or doing wrong?
#>
#>Thanks in advance for any help.
#>
#>Chuck

I'm still having the same problem. For example, I've downloaded
Macenvy from sumex into my Mac. I debinhex it with Stuffit 1.5.1,
which creates a StuffIt archive. The archive says there is a cdev
and documentation in it. I can extract the documentation and read
it. But when I extract the cdev, it doesn't function as a cdev
and acts just like a forlorn, forsaken document without an
application. I suppose I could learn to use ResEdit and fix
this, but isn't there an easier way?

Steve Goldfield