CAPUTE!
Modifications or Corrections To Previous Articles
Apple Games In ProDOS
Most of the Apple game programs recently published in COMPUTE! fail to operate properly with Apple's new ProDOS operating system, although they all work with DOS 3.3. The programs suffer from the same bug: Their graphics were developed using the DOS 3.3 version of the "Apple SuperFont" utility (published in the April 1985 issue). To use the following programs with ProDOS, these changes are required:
For "Mindbusters" (April 1985, p. 54):
120 POKE 6,0 : POKE 7,141 : PRINT CHR$(4);"PR# A$300" 450 PRINT CHR$(4); "PR#0"
For "Space Caverns" (March 1985, p. 54):
910 HOME: HGR : POKE 6,0 : POKE 7,141 : PRINT CHR$(4) ;"PR# A$300"
For "Bowling Champ" (February 1985, p. 126):
130 HOME : POKE 230,32 : CALL 62450 : HGR : POKE 6,0: POKE 7,141 :
PRINT CHR$(4);"PR# A$300"
830 X = 0: FOR I = 768 TO 853 : READ A:X = X + A : POKE I, A :
NEXT : IF X < > 7950 THEN PRINT "ERROR IN DATA STATEMENTS
FOR ML AT 76 8." : STOP
840 DATA 216, 133, 69, 134, 70, 132, 71, 166, 7
For "Paratrooper" (January 1985, p. 72):
200 FOR I = 768 TO I + 85: READ A:X = X + A :POKE I, A :
NEXT : IF X < > 23417 THEN PRINT "ERROR IN DATA STATEMENTS." : STOP
220 PRINT CHR$ (4)"PR# A$300"
1130 DATA 216, 133, 69, 134, 70, 132, 71, 166, 7
For "Things in the Dark" (December 1984, p. 79):
770 HOME : HGR : POKE 6,0: POKE 7, 141: PRINT CHR$ (4) " PR# A$300"
990 X = 0: FOR I = 768 TO 853 : READ A:X = X + A :
POKE I, A: NEXT : IF X < > 7950 THEN PRINT
"ERROR IN 1ST SET OF DATA STATEMENTS." : STOP
1000 DATA 216, 133, 69, 134, 70, 132, 71, 166, 7
For "Spiders" (November 1984, p. 96):
160 CALL 36884
In addition, ProDOS filename conventions require that you BSAVE the machine language portion of Spiders (Program 6) with the title SPIDER.2 instead of SPIDER 2 as indicated on p. 90. You'll also have to change SPIDER 2 to SPIDER.2 in line 130 of Program 5.
Atari Disk Rx
The author of this utility program from the March issue (p. 107) has provided the following corrections: Renumber line 4015 to become line 4006, replace the old line 4015 with 4015 REM, change the GOTO HALT in line 5075 with GOSUB HALT, and change the REC = 1 in line 6040 to REC = 0.
It is also possible for the program to crash with the message ERROR 5 IN LINE 325 while you are attempting to recover large files. The error occurs because the program does not check for buffer overflow. To prevent this, reader Jim Owens suggests adding and changing the following lines:
323 IF FILL = 1 AND (BCNT + TYPE)>RAM THEN ? : ?
"BUFFER FULL. LAST BUFFER SECT = ";SECT-1 : POP : GOTO 330
326 NEXT SECT
330 IF DIR = 1 THEN RETURN
Apple SuperFont
There are two typos in the checksum program (Program 6, p. 137) for this custom character utility for the Apple II series in the April issue. Lines 140 and 150 should read as follows:
140 FOR J = 0 TO 63:S = S + PEEK (4096 +I * 64 + J): NEXT 150 READ A:S = S - 256 * INT (S / 256)
Plus/Term For VIC & 64
In addition to the items in last month's "CAPUTE!" column, there is another correction to the machine language portion for the VIC-20. Whenever you load a file into the buffer, the lower boundary of the buffer is reset incorrectly so that 256 bytes of garbage are added to the start of the text. To remedy this, reset the VIC by turning it off and back on. Load the machine language data by typing LOAD "PLUS/ TERM.ML",8,1 (for tape, replace the ,8,1 with ,1,1). Then enter the following line in direct mode (without a line number):
POKE 43,0: POKE 44,24: POKE 7075,64
Immediately save the revised version by typing SAVE "PLUS/ TERM.ML2",8 (or ,1 for tape). Now change line 100 of the BASIC portion to reflect the new name for the machine language portion.
If your printer is not properly handling upper- and lowercase characters, try changing line 1900 to 1900 OPEN 5,ZE,7.
The article states that changing the baud rate after other parameters have been set causes all other parameters to revert to their default values. Actually, even though the various submenus will show all parameters reverted to their default states, the actual parameter values will not have changed. Thus, the menus will not reflect the actual settings of the parameters. For this reason, you should always change the baud rate before changing any other parameter.