Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!ads.com!killer!usenet
From: anders@verity.com (Anders Wallgren)
Newsgroups: comp.sys.mac.programmer
Subject: Re: How to load MacsBug?
Message-ID: <1991Apr12.212901.25120@verity.com>
Date: 12 Apr 91 21:29:01 GMT
References: <63682@bbn.BBN.COM>
Sender: usenet@verity.com (USENET News)
Reply-To: anders@verity.com (Anders Wallgren)
Distribution: usa
Organization: Verity, Inc., Mountain View, CA
Lines: 8
In-Reply-To: idowell@bbn.com (Ian Dowell)

I had this problem once and it turned out that using some software,
like Virtual and Maxima, replace the 'debugger' string that the system
uses to load the debugger with one of their own load files, and then
load macsbug if it's present.  Using SUM DiskTools, or some other disk
boot-block reader, check to make sure that the "debugger" string is
MacsBug and not something else.

anders