rknop@nntp-server.caltech.edu (Robert Andrew Knop) (01/14/91)
You GEOS 128 programmers are going to go nuts over this one:
You all have heard the story about how BSW decided to drop the geoProgrammer
2.0 project, even though they had made significant progress. Well, as it
turns out, geoDebugger 2.0 was basically finished. Better than that, pretty
soon we will all be able to get ahold of it!!!!!!
Note that it is intended ONLY as an upgrade to geoProgrammer 1.X, and
therefore only REGISTERED GEOPROGRAMMER OWNERS are legally allowed to
download and use this program. That being said, let me include the most
recent word we've seen on Q-Link from Berkeley in the person of Jim
Collette:
SUBJ: GREAT geoDebugger news... (R2) FROM: GEOREP JIM 01/12/91 S#: 413025
Well, this week I received some info from BSW about geoDebugger... more
specifically, a whole slew of info relating to the whole geoProgrammer package
in general, with 2.0 notes and all that.
While reading through this, I found one VERY interesting, and great thing about
geoDebugger 2.0 that I had no idea even existed:
The BackRam 128 Debugger.
Yes, it runs in the back RAM!! The complete functionality of SuperDebugger
(actually, it can hold MORE symbols, if I read it right) with NO REU
requirements!
This means there should be no conflict with geoWizard, and even better it means
that it doesn't matter whether you have a 17xx or GEORAM, since it won't need
it at all!
Since there don't appear to be any real improvements in geoDebugger 2.0 for the
64 (it's mostly 128 stuff) I will put off the GEORAM version for now and upload
geoDebugger 2.0 as is. On the 64, it won't be much different from 1.1, so if
you have a GEORAM it shouldn't really matter anyway. With the 128, you will be
able to use the BackRam SuperDebugger which won't need the REU at all.
I will also be uploading the info that I received, as they sent it to me on
disk as well. It's a BIG file (over 100K) but I will compress it with LHArc and
it should shrink down quite a bit. I will also try to make a reduced version of
this file which contains the nitty-gritty info needed for using Debugger 2.0 on
the 128.
-Jim :)
--------------------------------------------------------------------------
I will grab the archive once Jim puts it on Q-Link, and upload it to Milton.
Of course, this will make my db128rboot obselete, but thats life! :)
-Rob
rknop@tybalt.caltech.edu
mford@umaxc.weeg.uiowa.edu (Mark Ford) (01/20/91)
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. This is the first time I have tried to upload there, so either I did something wrong, or you can not send anonymous submissions, or something. Two things about geoDebugger 2.0 that I liked right away. 1. It configures itself as the SuperDebugger on a C-128 even if you don't have an REU. 2. It works with the 80-column mode. The disassembling, typing in commands etc. is done in 40 column mode, but the application will display on the 80-column mode if you opened geoDebugger from the 80 column mode. The patch for the old debugger would only run in 40 column mode. When you open geoDebugger 2.0 from 80-column mode, switch your monitor to composite. It doesn't say to do this, but the 80-column screen just sits there. I thought it bombed the first time I ran it. When you want to see the application (like after hitting f7) then just switch back to RGB on your monitor. This is nice when you are debugging an 80 column application. There is a small geoWrite 2.1 document that comes with the geoDebugger 2.0 (it is a self- dissolving ARC or whatever). I couldn't read it because I don't have version 2.1. I would have placed it at milton, but I couldn't figure out how. Any ideas? Mark mford@umaxc.weeg.uiowa.edu
rknop@nntp-server.caltech.edu (Robert Andrew Knop) (01/20/91)
mford@umaxc.weeg.uiowa.edu (Mark Ford) writes: >Two things about geoDebugger 2.0 that I liked right away. >1. It configures itself as the SuperDebugger on a C-128 even if you don't >have an REU. This is the BackRAM debugger, and you can force its configuration on a 128 by holding down the space bar while it is loading. Indeed, on a 128 you should always do this, because if the debugger goes into the REU it will thrash the RAM Rboot code, but won't in BackRAM. >I would have placed it at milton, but I couldn't figure out how. >Any ideas? I'm working on getting it at milton, and expect it to be there Monday, so don't worry about it. -Rob Knop rknop@tybalt.caltech.edu
rknop@nntp-server.caltech.edu (Robert Andrew Knop) (01/20/91)
As I said a couple of posts ago, I am working on getting geoDebugger 2.0 up at milton, and I expect it'll be there sometime Monday. For those of you who can't wait the extra day or two, send me email at rknop@tybalt.caltech.edu and I'll get you an "advance copy." IMPORTANT NOTICE: geoDebugger 2.0 is NOT public domain software. Since BSW has become preoccupied with the IBM, and never finished the geoProgrammer 2.0 package, that upgrade was never released in a "traditional" manner. Berkeley has been very kind to "Informally" release geoDebugger2.0, but it is released ONLY as an upgrade for REGISTERED GEOPROGRAMMER USERS. I know it may sound repetitive to keep saying this, but the 2.0 Debugger is a damn good upgrade for 128 programmers, and we should be very grateful to Berkeley for making it available. If we abuse the system overmuch, software companies may not be inclined to be so kind to loyal customers in the future. Lecture mode of... :) -Rob Knop rknop@tybalt.caltech.edu
rknop@nntp-server.caltech.edu (Robert Andrew Knop) (02/12/91)
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