Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!ksand
From: ksand@Apple.COM (Kent Sandvik, 120dB or more)
Newsgroups: comp.unix.aux
Subject: Re: A/UX and System 7
Message-ID: <13213@goofy.Apple.COM>
Date: 27 Apr 91 19:07:44 GMT
References: <51916@apple.Apple.COM> <1991Apr24.111305.454@skbat.csc.ti.com> <62.+HS-@smurf.sub.org>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 32

In article <62.+HS-@smurf.sub.org> urlichs@smurf.sub.org (Matthias Urlichs) writes:
>In comp.unix.aux, article <1991Apr24.111305.454@skbat.csc.ti.com>,
>  dittman@skbat.csc.ti.com (Eric Dittman) writes:
>< In article <51916@apple.Apple.COM>, ksand@Apple.COM (Kent Sandvik) writes:
>< > Now speaking about System 7, A/UX traps all kinds of A-line traps that
>< > the apps and standalone code (inits, DAs, CDEVs...) trigger. Any System
>< > 7 specific traps and glue can't be handled by A/UX, i.e. it does
>< > not understand for instance anything with the Edition Manager, and how
>< > to route these calls.

>Hmmm, I thought the Edition Manager and things are just new A-line traps.
>Shouldn't they get dispatched just fine?

Well, the QuickDraw routines are just mapped to the ROM ones, so that's
no problem, but the RAM-based calls are more problematic. Remember, the
System running is not a standard MacOs release System. In many cases
the A-traps that are related to OS issues (memory, file I/O and so on)
are converted to A/UX UNIX system calls.

Depending on the scope of emulation provided from before some things
may or may not work as they are (like the ADSP driver which was not
officially supported in A/UX 2.0).

I'm not 100% sure about the Edition Manager and Apple Events, but I have 
a feeling that the expanded event record will be something that
has to be taken care of (as well as support for core AppleEvents in the
MF, and a lot of other small System 7 issues).

Kent Sandvik 
-- 
Kent Sandvik, DTS Rock Lobster
Disclaimer: I am not working with Public Relations.