Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: System 7.0 Q & A -- memory protection (none)
Message-ID: <7383@hoptoad.uucp>
Date: 20 May 89 19:35:34 GMT
References: <1838@internal.Apple.COM> <7320@hoptoad.uucp> <1906@internal.Apple.COM> <7350@hoptoad.uucp> <364@taniwha.UUCP> <7357@hoptoad.uucp> <31132@apple.Apple.COM>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 16

In article <31132@apple.Apple.COM> phil@Apple.COM (Phil Ronzone) writes:
>Tim, Paul is correct. A/UX uses the exact same ROM as the Mac OS. And boy,
>does it run in 32-bit mode. Stacks, heaps, the video RAM, the mapped in
>address of the ROM, they are all over the place (i..e, not just in the
>first 16MB of address space). I.e., even now the ROMs are dealing with
>a 32-bit world.

Then why does the seventh question and answer under "32-Bit Addressing"
in the "Developer Conference Q&A" in the current developer mailing say
that a ROM upgrade will likely be required to run in 32-bit mode?  Also,
do A/UX applications running in 32-bit mode make calls to the various
parts of the Toolbox that are needed by MacOS applications, such as the
resource manager?
-- 
Tim Maroney, Consultant, Eclectic Software, sun!hoptoad!tim
"Gorbachev is returning to the heritage of the great Lenin" - Ronald Reagan