Commodore Plus/4 Loading Error Messages and Fixes

The Commodore Plus/4 frequently displayed specific BASIC error messages when failing to load software from tape or disk. This guide identifies the most prevalent load failures, explains their technical causes, and offers solutions for hardware and media issues.

The most infamous message encountered by Plus/4 users was the ?LOAD ERROR. This generic notification indicated that the computer received data from the storage device, but the verification process failed. When loading from cassette, this usually pointed to poor tape quality, incorrect volume settings on the datasette, or misaligned tape heads. Since the Plus/4 featured a built-in tape interface rather than an external port, internal connection issues could also trigger this failure. For disk users, a ?LOAD ERROR often suggested a dirty drive head or a scratched disk sector preventing the system from reading the checksum correctly.

Another common interruption was the ?FILE NOT FOUND error. This occurred when the command specified a filename that did not exist on the media or when the directory structure was corrupted. On tape systems, this message appeared if the user attempted to load a program located further down the tape without winding past the initial files. Disk users typically saw this if the drive was not properly initialized or if the file extension did not match the search parameter used in the LOAD command. Ensuring the correct device number was specified, usually device 1 for tape and device 8 for disk, was crucial to avoiding this message.

Users also frequently encountered the ?DEVICE NOT PRESENT error during the initialization phase of loading. This critical error meant the computer could not detect the peripheral hardware at all. For tape loading, this often resulted from a broken cable inside the unit or a malfunctioning motor control signal. In disk configurations, it usually indicated that the floppy drive was powered off, the serial cable was loose, or the drive number was conflicted with another device on the serial bus. Troubleshooting this required checking physical connections and ensuring the peripheral was powered on before the computer attempted to handshake with it.

Less common but still problematic was the ?OUT OF MEMORY error during loading. This happened when the program being loaded was larger than the available RAM or when the load address overlapped with critical system memory used by the Plus/4’s 3+1 architecture. Because the Plus/4 reserved specific memory ranges for its built-in software suite, programs designed for the Commodore 64 often triggered this error if they attempted to write to protected addresses. Users had to ensure they were loading software specifically compiled for the Plus/4 hardware to prevent memory conflicts from halting the loading process.