Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cuae2!ihnp4!cbatt!ucbvax!ernie.Berkeley.EDU!shebanow
From: shebanow@ernie.Berkeley.EDU.UUCP
Newsgroups: comp.sys.mac
Subject: Re: Let's do _Launch
Message-ID: <17352@ucbvax.BERKELEY.EDU>
Date: Fri, 13-Feb-87 13:37:21 EST
Article-I.D.: ucbvax.17352
Posted: Fri Feb 13 13:37:21 1987
Date-Received: Sat, 14-Feb-87 23:44:24 EST
References: <1033@gould9.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: shebanow@ernie.Berkeley.EDU.UUCP (Mike Shebanow)
Organization: University of California, Berkeley
Lines: 19


Here's what I know about _Launch. You can pass a full pathname to _Launch,
and it will work. However, some programs use the default volume (which is
supposed to be the volume/WD where the application resides) to determine
where to find files, relative to the application's location. Although I
am not positive, I believe that _Launch is NOT smart enough to set the
default volume if you pass a full path name. So for compatibility's sake,
I would recommend that you do a setvol to the WD of the folder containing
the application. Of course, it is quite possible that no such WD exists,
so you may need to create one.

Personally, I had a lot of trouble with my MDS (anyone remember MDS?) style
transfer menus when HFS was released. I solved the problem, but it was a lot
of work. I think that Apple should get smart and provide a more intelligent
_Launch, in the same way that the 128K ROMs provided a more intelligent
_OpenResFile.

Andrew Shebanow
(Please do not reply directly to this account)