Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!husc6!panda!genrad!decvax!decwrl!dec-rhea!dec-exodus!harrow
From: harrow@dec-exodus.UUCP
Newsgroups: net.micro.mac
Subject: Re: ETIcon problems...
Message-ID: <2921@decwrl.DEC.COM>
Date: Mon, 12-May-86 16:52:12 EDT
Article-I.D.: decwrl.2921
Posted: Mon May 12 16:52:12 1986
Date-Received: Wed, 14-May-86 20:43:35 EDT
Sender: daemon@decwrl.DEC.COM
Organization: Digital Equipment Corporation
Lines: 21

Brian recently  responded  with  some  suggestions on how to work 
with the resources of his ETIcon application (THANKS!, Brian).  I 
thought I'd comment on the "fix" that I ended up using:

Since I know that  the  resources  WERE in the working standalone 
application (distributed with the sources), I added the following 
in the _INIT procedure:

OpenResFile ("ETIconed");

This opened the distributed application as  just a resource file, 
and read things from there as needed.

Scott (at Reed) also indicated that the Linker does NOT re-create 
a new file, but only replaces the code  segments.   Hence, if you 
one-time create a standalone application file with  your  ResEdit 
resources, just use  that  filename  as the output for the Linker 
(via the BATCH facility?)  and the resources will stay there, but 
you newly compiled code will be inserted.

Jeff