Conference hydra::amiga_v1

2260.0. "Set Requestor Text from CATS" by CGOU01::OAKLEY (What am I doing here...) Tue Feb 21 1989 20:12

Here's a new little goodie from Carolyn S. @ CATS
    
    ------------------------------------------
        
For your beta testing pleasure...

SRT (Set Requester Text)  v1.31   by  Carolyn

Usage: SRT file|RESET|?   (default text file - s:srt.text)

This program installs a wedge into AutoRequest for the purpose
of replacing the text of standard system requesters.

SPECIAL BONUS (but wait! there's more!)

If your replacement text for "Software error - task held" is "DEBUG",
SRT will replace those useless Software Error requesters with a full
width display of the PC, SP, registers, task address, and name of the
task/command/process that crashed.  And the left gadget will now allow
you to get rid of the requester and just have that task wait forever.

You can even install srt AFTER you have crashed, if you can pop up a
CLI to install it from.  Just install srt then click RETRY in your old
SW Error Task Held requester.  The new requester will be the full width
srt debugging requester.  Handy for those of us who don't plan ahead.


You provide the replacement text in an ascii file of the following
form:

N=linecount
"old text" "new text"
"old text" "new text"
etc.

I have provided a sample file called "srt.text".

S:srt.text is the default text file for srt.  If you place srt.text in
your s: directory, you can install srt by just typing SRT<ret>.
 
If you have a different replacement text file, just pass it as CLI arg:

Example:   SRT myreq.text


I have also provided several small programs (each called crashN where
N = the number of the exception the program causes).

After installing SRT (with my srt.text), you can test the new DEBUG requester
by running any of those programs >NIL:.

Example:   run >NIL: crash8


I think I've now got it working right for both 68000 and 68020,
but would appreciate somebody testing "crash3" on a 68020 and
making sure the PC shown is correct (it should show a value within
about 4 bytes of the value shown in one of the A registers).
(Each of my "crash" programs stores sequential numbers in the
registers, then stores its own SP and PC in two of the A registers
prior to causing the crash, so I can visually check that the DEBUG
requester SP and PC displays are correct).


    

    The kit is at cgou01::amnew:srt.zoo
    
    wayne