The Worx

The Worx is a file-management shell program that organizes multiple data areas in memory, providing a menu-driven interface for loading and saving three distinct file types: a PLAN file (a planner/calendar), a FONE file (a phone directory), and up to five Virtual files stored in a block starting at address 57374. The program uses machine code loaded from tape into address 29850, with additional code blocks at 60909, and interrogates system flags via PEEK at address 65533 to determine whether to enter the main menu or trigger an auto-save prompt on exit. A status bar is displayed on line 1 of the lower screen using PRINT #1 with PAPER and INK colors read dynamically from PEEK 65531 and 65532. The virtual file print routine reads filenames stored at fixed memory offsets (52242–52251 for the system name, 57374+ for virtual file headers) and sends file contents directly to the printer via LPRINT.

Program Structure

The program is organized into loosely grouped functional blocks by line number range:

• Lines 1–10: Initialization — calls machine code at 29850 via RANDOMIZE USR, then PEEKs address 65533 to branch either to the main menu or the exit/save prompt.
• Lines 1000–1100: Main file-options menu, displaying choices and dispatching on single-key input.
• Lines 1110–1170: Virtual file print routine — lists up to five virtual files and sends selected file contents to the printer.
• Lines 1400–1620: Subroutines for virtual file input, load, and save.
• Lines 4000–4010: Header display subroutine — reads a system name from memory at 52242–52251 and prints it inverse.
• Lines 5000–5050: Exit handler — prompts to save PLAN and FONE files before quitting.
• Lines 9000–9060: Tape load sequence for the full Worx suite (BASIC, screen, two CODE blocks).
• Lines 9500–9610: Backup routine — offers tape SAVE of the entire suite.
• Lines 9800–9880: PLAN and FONE file load/save subroutines at fixed addresses.
• Lines 9900–9910: System re-initialization — writes color and mode flags into the system variables area and jumps to the main menu.
• Lines 9992–9998: Utility lines for saving the BASIC shell itself and a commented-out NEW command.

Machine Code Usage

Line 1 calls RANDOMIZE USR 29850 before CLEAR, invoking a machine code routine loaded from tape as TSWORX.CB (29850, length 21751 bytes) and a second block as TSWORX.CC at address 60909 (4599 bytes). These routines almost certainly provide the core application logic — the BASIC shell acts primarily as a loader and menu interface around them. The CLEAR 29849 in line 9002 positions BASIC’s memory ceiling just below the first machine code block, protecting it from BASIC’s variable area.

Memory Map

Address	Purpose
29850	Machine code block 1 (TSWORX.CB), 21751 bytes
52242–52251	System name string (10 chars), displayed in header
52894	PLAN file data, 1280 bytes
54174	FONE file data, 3200 bytes
57374	Virtual files block start (5 × 672 bytes = 3360 bytes)
57406	Virtual file data payload start (offset +32 from block start)
60909	Machine code block 2 (TSWORX.CC), 4599 bytes
65530–65533	System flags: color/mode settings and exit-state flag

Key BASIC Idioms and Techniques

• Single-key polling loop: Lines 1010–1100 use INKEY$ in a tight loop with an empty-string check, a standard approach for responsive menu navigation without waiting for ENTER.
• PEEK-based system flags: Address 65533 is polled at line 10 to decide between normal startup and an exit-save path, and addresses 65530–65532 are POKEd in line 9900 to set paper/ink/mode for the session.
• Dynamic status bar: Line 1005 uses PRINT #1 to write to the lower screen with PAPER PEEK 65531; INK PEEK 65532, reading live color values from memory rather than hardcoding them.
• Memory-title construction: The subroutine at line 4000 builds a display string by concatenating CHR$ PEEK over a 10-byte range, pulling a stored system name directly from RAM.
• CAT command: Line 1405 uses CAT ".C*" to list matching files before prompting for a filename — useful for reminding the user of available virtual files on disk/microdrive.
• Fixed-stride virtual file layout: Virtual files are accessed with stride 672 bytes, with the filename header in the first 32 bytes and 640 bytes of printable content. The print loop (lines 1120–1170) uses x=57406+((VAL f$)-1)*672 to locate the correct block.

Bugs and Anomalies

• Case mismatch at line 1085: The condition uses A$ (uppercase) rather than a$ (lowercase) as used throughout the rest of the program. On most implementations this will still work since BASIC variable names are case-insensitive, but it is inconsistent.
• Line 9998 comment: The line reads REM RANDOMIZE USR 100:NEW — a NEW command inside a REM is harmless, but the RANDOMIZE USR 100 suggests a placeholder or earlier entry point that was commented out rather than deleted.
• Line 8000 orphan: POKE 65533,4:GO TO 1 is defined but never called from anywhere visible in the listing. It may be a developer utility or a hook intended for machine code to invoke.
• STOP key string: Line 1020 tests a$="STOP " with a trailing space. Since INKEY$ returns a single character, this string can never match, making the back-navigation via SS/A non-functional from within the file menu. The status bar message is therefore misleading.