VDRIVE is a modular disk routing protocol for the Commodore 64. With WiC64 hardware, it allows users to search, mount, and share disk images directly from their C64 using simple BASIC calls. Once mounted, PRGs can be loaded or saved, enabling persistent workflows across multiple systems.
WiC64 is memory‑mapped directly to the C64, bypassing the limitations of serial communication and enabling near‑instant loading of large binaries.
11/28/2025 –
VDRIVE 1.0.0-beta
is now on GitHub! Run a VDRIVE server locally and point it to your disk images and PRGs.
Core functionality includes
SYS 49158 — Search for disk images using a keyword or label
SYS 49161 — Remount a disk from the previous search result
Key Components
VDRIVE Server — C# .NET Core tooling that implements resolvers, adapters, and host‑side logic for serving disk images to WiC64.
IFloppyResolver — Resolves search terms into disk image paths (local or remote).
IStorageAdapter — Abstracts the file system or remote storage layer for mounting, reading, and writing disk images.
VDRIVE C64 Client — The C64‑side component written in 6510 assembly. Communicates via WiC64 memory‑mapped I/O and handles user input and disk mounting logic.
Floppy resolvers include configurable local path scanning or remote search/mount with Commodore.Software. Storage adapters include c1541.exe from VICE and CBMdisk.pyd that powers DirMaster.
Memory region — VDRIVE runs at $C000. Any LOAD into that region will crash. By default, VDRIVE returns “file not found” if a load targets a known crash‑prone area.
VDRIVE is functional, but still evolving. Expect rough edges — and feel free to contribute or fork.