Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!ephemeral.ai.toronto.edu!dudek
From: dudek@ai.toronto.edu (Gregory Dudek)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Mac+ Programmers Interupt Bug
Summary: Maybe to have another "debugger" installed?
Keywords: interrupt, debug, macsbug, autoblack
Message-ID: <89Aug29.113250edt.11269@ephemeral.ai.toronto.edu>
Date: 29 Aug 89 15:33:51 GMT
References: <11098@boulder.Colorado.EDU>
Organization: Department of Computer Science, University of Toronto
Lines: 22

In article <11098@boulder.Colorado.EDU> domingo@boulder.Colorado.EDU (Alberto Domingo) writes:
>The Programmers Interrupt key of my Mac+ (10th day out of warranty)
>does not work. It hangs the Mac, but the window does not appear!.
>... I think it is not a *mechanical* problem.
>
  There's a handy INIT named "autoblack" that installs itself like
a debugger.  If you use it, and DON'T have a real debugger installed as well,
the problem you describe may appear.  The system thinks that you have installed
an alternate RAM debugger, thats why the ROM debugger doesn't work.

  To further compilcate things, the "autoblack" INIT is usually
named "MacsBug" in your system folder.  If you have a file named "MacsBug",
try renaming it to something else & rebooting.  It's also possible that
you actually have the real MacsBug program there, but it is damaged.

  Greg Dudek
-- 
Dept. of Computer Science (vision group)    University of Toronto
Nice mailers:  dudek@ai.utoronto.ca
UUCP: {uunet,decvax,linus,pyramid,
		dalcs,watmath,garfield,ubc-vision,calgary}!utai!dudek
ARPA: user%ai.toronto.edu@relay.cs.net