🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.mac
Article #15894

Re: Change in "_Launch" interface...

#15894
From: Larry Rosenstein
Date: Mon, 04 May 1987 20:17
57 lines
2828 bytes
In article <MUa8YYy00UhTQM00cm@andrew.cmu.edu> rs4u#@ANDREW.CMU.EDU (Richard Siegel) writes:
>
>Some questions:
>
>	1) Why the change? It seems to me that there's a large number
>of programs that have the "Transfer" feature (as it's usually called),
>that will suddenly stop working.

Not likely.  The sublaunch code simply adds a new feature to _Launch, it
doesn't change anything else.  The mechanism for passing additional
parameters to _Launch was implemented in the 128K ROM, and as far as I know
they have never been documented.

In the 128K ROM, these extra parameters were used to indicate that a program
should be launched read-only, which is useful if you are using a file
server.

>	2) For Old Mac and Mac Plus owners (Old Mac = 64K ROM), does
>this change come with System 4.x? Or is it simple a change in the ROM
>for the SE and Mac II, so the "Transfer" feature will only crash
>on the new machines?

The patch is definitely in System 4.1; I don't have a copy of System 4.0
around to see if it was in there as well.

>	3) *Flame On* Why is Apple doing this? I personally would simply
>add another trap (_SubLaunch or somehting) to the 256K ROMs, or
>make the existing _Launch trap smart enough to know when it's being

The new features are activated by a special signal to the _Launch trap.
Normally, _Launch takes a pointer to a parameter block in A0.  The first
long of the block points to the file name and the next 2 bytes to the
sound/screen page 2 options.  

If the 2 bytes after that is $4C43, then the extended parameter set is
assumed.  Following the code will be 4 bytes for the length of the extended
parameters, followed by a word of flags. Bit 6 of the low flag byte is 1 to
indicate a read-only launch.

As I mentioned before, I don't have a copy of the new set of Tech Notes,
which indicate how to specify a sublaunch.

>	4) By the way, will this interface change be backward compatible?

If the patch is not present, then the sublaunch will work, but (I assume
that) the application doing the launching would not regain control.


-- 
Larry Rosenstein

Object Specialist
Apple Computer

AppleLink: Rosenstein1
UUCP:  {sun, voder, nsc, mtxinu, dual}!apple!lsr
CSNET: lsr@Apple.CSNET
Technical Details
Message-ID: <708@apple.UUCP>
Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!lll-lcc!pyramid!voder!apple!lsr
References: <MUa8YYy00UhTQM00cm@andrew.cmu.edu>

Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!lll-lcc!pyramid!voder!apple!lsr
From: lsr@apple.UUCP (Larry Rosenstein)
Newsgroups: comp.sys.mac
Subject: Re: Change in "_Launch" interface...
Message-ID: <708@apple.UUCP>
Date: Mon, 4-May-87 16:17:40 EDT
Article-I.D.: apple.708
Posted: Mon May  4 16:17:40 1987
Date-Received: Tue, 5-May-87 05:38:32 EDT
References: <MUa8YYy00UhTQM00cm@andrew.cmu.edu>
Reply-To: lsr@apple.UUCP (Larry Rosenstein)
Organization: Advanced Technology Group, Apple Computer
Lines: 57