Tardis DOS v0.1.82

What's new since v0.1.76

• sys <addr> command — call machine code in place, like BASIC's SYS (e.g. a SIDKick pico's sys 54301 / sys 54333). Decimal by default, hex with $. Runs under Tardis, not stock ROMs — great for KERNAL-API routines and I/O-device triggers; use run for programs that need stock KERNAL/BASIC.
• run reliability fix — a loaded program now actually starts after the stock-ROM swap. It auto-types RUN into stock BASIC's own machinery instead of a direct interpreter jump that came up blank on real hardware.
• Tab completion survives errors — a failed cd/rm/mv/cp no longer wipes the completion cache; only a successful one does.
• Meaningful offline errors — load / cd of a networked file report 74 DRIVE NOT READY when the drive is offline, vs 62 FILE NOT FOUND for a genuinely missing file (pairs with a Meatloaf-side change). Drive-status output now has a space between the code and the message.
• pwd asks the drive's PWD command first (Meatloaf network path), falling back to the disk header.

Downloads — pick the binary for your exact board

Hardware	Board	File
Breadbin C64 (separate 24-pin KERNAL/BASIC)	fire-24-e	c64-tardis-dos-v0.1.82-for-onerom-fire-24-e.bin
Breadbin C64	fire-24-f	c64-tardis-dos-v0.1.82-for-onerom-fire-24-f.bin
C64C (single combined 28-pin ROM)	fire-28-a	c64c-tardis-dos-v0.1.82-for-onerom-fire-28-a.bin
C64C	fire-28-c	c64c-tardis-dos-v0.1.82-for-onerom-fire-28-c.bin
C128 (Tardis as the C64-mode ROM in U32; use GO64)	fire-28-c	tardis-c128-v0.1.82-for-onerom-fire-28-c.bin

Firmware is board-specific — a binary for one board won't run on another. Match your exact board (onerom scan --list-boards).

Notes

• The C64C binaries serve no character ROM, so font is unavailable (the charset stays the boot font); everything else works. Not yet validated on real C64C silicon — only in C128 C64-mode, which is the same combined-ROM path. Sanity-check boot + a couple of overlay commands after flashing.