Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!apple!justin
From: justin@Apple.COM (Justin Walker)
Newsgroups: comp.unix.aux
Subject: Re: MacsBug under A/UX 2.0
Message-ID: <50672@apple.Apple.COM>
Date: 23 Mar 91 04:27:42 GMT
References: <119@mishima.mishima.mn.org> <12567@goofy.Apple.COM>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 33

In article <12567@goofy.Apple.COM> ksand@Apple.COM (Kent Sandvik) writes:
>In article <119@mishima.mishima.mn.org> spencerc@mishima.MN.ORG (Spencer Crum) writes:
>> ...
>I assume that you try to drop to MacsBug with the NMI button, or programmer's
>key. Well, the NMI drops you down to kernel never-never land because it
>signals the CPU directly. The trick under A/UX for dropping down to MacsBug
>is to press command-control-E (command-control-I) kills the current MultiFinder
>process, so if you get jammed, that's the trick).
>
	To clarify this: cmd-ctrl-e "reboots" the current MultiFinder
session (gets you back to the Login screen).  cmd-ctlr-i drops you
into MacsBug if you have it installed in the System Folder you are
executing from.  Without MacsBug installed, cmd-ctrl-i has a similar
effect to cmd-ctrl-e.

>Regards,
>Kent

Cheers,

Justin

Justin C. Walker, Curmudgeon-At-Large   *
A/UX Engineering                        |
Apple Computer, Inc.                    |  Try visualizing whirled peas.
10300 Bubb Rd,                          |
Cupertino, CA 95014                     *
-- 
Justin C. Walker, Curmudgeon-At-Large   *
A/UX Engineering                        |
Apple Computer, Inc.                    |  Try visualizing whirled peas.
10300 Bubb Rd,                          |
Cupertino, CA 95014                     *