BUG-65 Version 2.0 Manual with ERRATA ; size: 2.7 MB ; this manual contains as the only one an error page: 'ERRORS IN YOUR BUG/65 MANUAL' (page 4 in the pdf file). As of this moment, it is not understood, why the there mentioned commands: N, O, R', R", W' and W" do not work with the above version 2.0 of BUG/65. Either we have version 1.1 for real, while 2.0 is shown at start or something else is wrong here. Anyway, the mentioned pages on the error page do match with pages in the rest of the manual. Further, the below mentioned BUG/65 version 4 patch should not be done, according to the error page from December 1983(?), while it should be done according to the OSS newsletter from summer 1983. Maybe just the 'old boys club' from the golden age can solve this? Any help in that case is very welcome at any time. We would really appreciate if you may can help us here. :-)

Please take into account, that in the manuals above version 1.1 is mentioned, while just version 2.0 is available up to now. If you own version 1.1, please let us know. We can make you an offer, you can't resist. ;-)

Mega-thanks to Erhard Pütz for the final solution of this problem! :-)

Device ID $3F instead $40. BUG/65 jumps indirect into the put-byte-routine of the OS ($E436 -> $FECA+1), therefore no IOCB-channel is opened and the device number is missing.
Patch (thank you ep for the solution!):
Load BUG/65 and change the following:

The above program named as "BUGV4FIX.BAS" is in form of a file already on all of the atr-images above.

To make the patch to BUG/65 do as follows:
1) Insert your BASIC cartridge or use BASIC A+ disk.
2) Place your BUG/65 disk into the disk drive.
3) Use this BASIC program above to apply the one byte patch so that BUG/65 will work with OS/A+ version 4.

b):
machine language program:

name of file: BUGV4FIX.COM

BUGV4FIX.COM ; we are still searching for that file, it seems to be lost. Any help, any hint in that case is very much appreciated. :-)

At the end of the BUG/65 manual we can read:

1. Copy the files BUG65.COM and BUGV4FIX.COM to a version 4 disk using the COPY24 command (see the DOSXL manual for details on this command).
2. At the version 4 "D1:" prompt, type the command: BUGV4FIX (RETURN).
3. The file BUG65.COM on that disk is now compatible with version 4 of DOSXL.

WARNING: Do NOT perform the BUGV4FIX command on your version 2 master disk!

When BUG gets control as the result of a BRK instruction being executed, it actually checks to see it the BRK instruction is one which it placed (as a result of a "G" command). If not, it assumes that it is a user breakpoint, to be handled by a user routine! Guess what? Most of us don't go around adding user BRK handlers to Atari’s OS, so the machine goes off into never-never-land.

Quick hix (again, not hor the faint of heart): After loading BUG/65 from CP, perform the following actions:

1. Display the contents of location $2E7 (LOMEM).
2. Use the "H" command to add $17EE to those contents. (Example: if $2E7 contains 2200, use "H 2200 17EE” to find the sum.) Call this value ADDSUM.
3. Display the memory at ADDSUM (via the "D" command. You should see the following bytes (if not, stop now): 39EE E9 02 4D . . . ("39EE" is arbitrary-value of ADDSUM if LOMEM is at $2200.)
4. Use BUG/65 commands as follows:

If you did everything correctly, BUG/65 should allow a "USER RUN" and then print a breakpoint message for the BRK at $60A. If it didn’t work, you may have an already-fixed version of BUG/65, so ignore all this.

In order to allow itself to be relocated virtually anywhere in memory, BUG/65 as shipped includes a relocation bit map and relocation program. In addition, relocatable BUG/65 always loads in at locations $9800 through $BC00. If these addresses are "poison" to you (e.g., if you want to use BUG/65 with a cartridge plugged in), you may wish to produce a non-relocatable version designed to run within an address range you pick. If so, USING A 48K SYSTEM, simply specify the loadpoint, as shown in the preceding section (e.g., via BUG65 7000) and allow BUG/65 to load and relocate. Then exit to OS/A+ (via Quit) and use OS/A+ intrinsic command SAVE to save a non-relocatable version. The address range to be SAVEd may be calculated as follows:

SAVE filename.com loadpoint+$200 loadpoint+$1FFF

Thus, if you had specified "BUG65 7000", you could save the non-relocatable version via

SAVE BUG7000.COM 7200 8FFF

thus also giving it a name which will later remind you where it will load at. To execute this non-relocatable version, simply type in its name (BUG7000 in the example shown).

• A full set of debugging commands - change memory, display memory, goto user program with break points, etc.
• Binary file read and write, including appended write
• A disassembler
• An instant assembler providing labelling capability
• Expanded command addressing capability: hex or decimal addresses, + and - operators supported, relocated addresses supported
• Read or write disk sector(s)
• Multiple commands permitted in a command line. Command lines can be repeated with a single keystroke or repeated forever with the special slash operator.
• Support for relocatable assemblers - the base of a module can be specified and then used to reference addresses in that module
• BUG/65 commands can be executed from a command file, and there is a command to create command files
• Hex to decimal and decimal to hex conversions provided
• Memory protection of BUG/65's code and data. BUG/65 won't allow you to use a BUG/65 command that will destroy any part of BUG/65 itself. For example, you can't use the Fill command to overwrite BUG/65's code.
• Page zero sharing. BUG/65 shares page zero with a user program by keeping two copies of the shared page zero locations - one for the user and one for BUG/65 itself.