Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!jarthur!nntp-server.caltech.edu!rknop
From: rknop@nntp-server.caltech.edu (Robert Andrew Knop)
Newsgroups: comp.sys.cbm
Subject: Re: geoDebugger 2.0
Message-ID: <1991Feb12.005154.8704@nntp-server.caltech.edu>
Date: 12 Feb 91 00:51:54 GMT
References: <4021@ns-mx.uiowa.edu>
Distribution: na
Organization: California Institute of Technology, Pasadena
Lines: 26

mford@umaxc.weeg.uiowa.edu (Mark Ford) writes:

>I downloaded geoDebugger 2.0 from Q-Link.  It is in the Berkeley Applications
>section.  There was also a monster file, (200+ blocks arc'd, 440+ unarc'd),
>that provided some details on geoDebugger 2.0.  I was going to send it 
>to milton.u.washington.edu, but it told me permission denied.

Don't worry about it- geoDebugger 2.0 is already there!  Indeed, you could
have saved yourself the Q-Link plus time (oh well....).  The monster info
file is also there.

>1. It configures itself as the SuperDebugger on a C-128 even if you don't 
>have an REU.

What you describe is the BackRAM debugger.  This has two advantages over the
REU superDebugger:

1) it runs on a 128 without an REU
2) the REU superDebugger thrases the RAM Rboot code in the REU- so if you want
   to rboot, you should use the BackRAM debugger even if you have an REU.  You
   can do this by holding down the space bar while the debugger loads, or, if
   you get tired of holding down the space bar, use my backdeug.patch (or
   similar filename) which is at milton.

-Rob Knop
rknop@tybalt.caltech.edu