Multiprogram Demo

Multiprogram Demo is a collection of demo versions of programs from the “Fun and Games” tape, with the main interactive piece being SYNCWARS, a keyboard-reflex game in which the player must destroy alien SYNCLOIDS and their hidden SYNCLON commanders by pressing the key corresponding to each enemy’s screen position. The game uses USR calls to machine code routines at addresses 16514, 16567, and 16608 for display and timing effects, and employs a position-calculation algorithm at line 2950 that maps random values to screen coordinates using division and modulo arithmetic. Enemy sprites are drawn using block graphics characters arranged in multi-line PRINT AT sequences, giving the illusion of structured alien figures. Numeric variables N0–N5 and O0 are pre-initialized via VAL literals as a memory-saving technique common in constrained BASIC programming. A SAVE command at line 1330 and CLEAR/RUN sequences suggest the tape contains a chained multi-program loader structure.

---

Program Analysis

Program Structure

The listing is organized into several distinct functional regions, reflecting a multi-program loader design:

1. Lines 1–8: REM headers (containing embedded data) and a GOTO VAL "2000" entry point.
2. Lines 10–30: A subroutine that POKEs values into address 16609 and calls USR 16608 twice, likely a display or border effect routine.
3. Lines 1325–1335: A CLEAR/SAVE/RUN block for chaining to the next program on tape (SYNCWARS-4K).
4. Lines 1510–1570: A subroutine (called from line 2880 when score equals 10) that cycles through screen rows, POKEing and USR-calling address 16514, and prints a “TOP SCORE” banner.
5. Lines 2001–2890: Main game initialization and game loop for SYNCWARS.
6. Lines 2910–2968: Sprite-drawing and position-calculation subroutines.
7. Lines 3000–3020: A short delay loop subroutine.
8. Lines 9300–9350: End-of-game display subroutine.
9. Lines 9995–9998: A secondary loader block using RAND USR 20480 to jump to machine code at address 20480.

Machine Code Usage

The program makes extensive use of USR calls to pre-loaded machine code routines. The results are assigned to the dummy variable M since BASIC requires a value to be returned from USR:

Address	Usage	Context
16514	USR 16514	Called in the top-score scroll (line 1540) and end-of-game sequence (line 9320)
16567	USR VAL "16567"	Called after POKEing a character code to 16568, used for character output (lines 2070, 2680)
16608	USR 16608	Called after POKEing to 16609, likely a border/display effect (lines 15, 25)
20480	RAND USR 20480	Loader entry point at line 9996

The POKE/USR pattern at lines 2050–2070 is particularly notable: a character code is POKEd to address 16568, then USR 16567 is called — this is a classic technique for driving a machine code character-output routine from BASIC, iterating over the characters of A$ to initialize some display or keyboard mapping table.

Numeric Variable Optimization

Lines 2001–2007 pre-initialize a set of short-name variables using VAL "n" literals:

• N0 = 0, N1 = 1, N2 = 2, N3 = 3, N5 = 5
• O0 = 10

Using single- or two-character variable names with VAL-encoded literals reduces the per-token storage cost of numeric literals throughout the program. The VAL "number" idiom also prevents the interpreter from storing a floating-point five-byte value inline in the tokenized line, saving memory especially when a constant is used many times.

Game Mechanics and Loop

The core game loop runs from line 2625 to 2870, iterating C from 1 to 10 (one round per enemy). Each iteration:

1. Calls GOSUB 2950 to randomly position the SYNCLOID (D,E,G) and SYNCLON (H,I,K) on screen, ensuring they don’t share the same slot.
2. Draws the SYNCLOID sprite (visible) via USR 16567 and GOSUB 2910.
3. Waits for a keypress in an inner loop; the available time decreases as C increases (O0-C/N3).
4. If the player hits the SYNCLOID’s key (A$(H+N1)), transitions to phase 2 (reveal/destroy the SYNCLON via GOSUB 2920).
5. If the player hits the SYNCLON’s key directly (A$(D+N1)), the shot is still counted valid (line 2707 falls through to the Synclon phase).
6. A miss displays a “>[*]<” marker and gives a brief second-chance window (lines 2850–2858).
7. Too-slow response triggers the “TOO SLOW” message at line 2820.

Position Calculation Subroutine

Lines 2950–2969 convert a random integer in range 0–37 to row/column screen coordinates:

• D = INT(RND*38) — random slot index
• E = INT(D/10) — row zone (0–3)
• G = (D - 10*E)*3 + E — column offset with spacing
• E = E*6 - 1 — final row coordinate

The same formula is applied independently for H/I/K (SYNCLON), with a collision check at line 2962 re-rolling if H=D. This maps 38 discrete slots onto a grid spread across the display.

Sprite Drawing

All sprites are drawn with multi-line PRINT AT row,col sequences using TAB to re-position within the same PRINT statement, building up a 5-row block-graphic figure. For example, the SYNCLOID sprite (line 2910) prints five rows of three characters each using TAB G to align each row. The destruction animation (line 2940) replaces the sprite with asterisk/block-graphic “explosion” characters.

Keyboard Mapping

The string A$ at line 2085 encodes the full keyboard layout in a single string: digits, then QWERTY... rows including CHR$ 118 (ENTER/NEWLINE) and ending with ZXCVBNM.. Enemy positions are mapped to indices into this string, so pressing the key at the corresponding position in A$ identifies a hit.

Scoring and Chaining

Score F is incremented for each successful destroy. At the end of 10 rounds (line 2875), the end-of-game screen is displayed. If F=10 (perfect score), the top-score subroutine at line 1500 is called. After the end screen, the game loops back to line 2560 (the instructions/start prompt). Line 1330 provides a tape-chaining save point, saving the next program as SYNCWARS-4K and immediately running it, suggesting this demo is part of a larger chained tape sequence.

Notable Anomalies

• Line 2880 calls GOSUB 1500 but the subroutine begins at line 1510; there is no line 1500, so execution falls through to 1510 — this is a deliberate technique, not a bug.
• Line 2890 jumps to VAL "2560" but line 2560 does not exist in the listing; line 2570 is the next defined line. Execution would therefore continue from line 2570 (the “PUSH ANY KEY” prompt), which is the intended behavior for restarting the game.
• The delay loop at lines 3000–3020 iterates only O0 (10) times, making it extremely short — effectively just a brief synchronization pause rather than a perceptible delay.
• Line 9998 (PRINT PEEK 16412+256*PEEK 16413) reads the system variable PROG and prints the start address of the BASIC program — likely a debugging remnant.