VICE

VICE (Versatile Commodore Emulator) is a Commodore 8-bit emulator collection that includes configurations for the Commodore 64 and Commodore 128. In this article it is considered as an environment for using applications, configuring controlled tests, and developing software on a later host computer, rather than as a claim of perfect hardware equivalence. When this candidate was sourced, the official site listed the stable release as VICE 3.10, released on 24 December 2025. That dated stable release is distinct from later development snapshots: the official Git mirror identifies itself as a mirror of the project’s Subversion repository and separately links snapshot builds of the latest code.

Project scope and configured execution

VICE’s project documentation describes machine-specific emulators and their settings, and the project site identifies SourceForge as a public source-repository service. Its GitHub presence is therefore best described as the official Git mirror, not as a second authoring project or a second independent technical root. A result obtained in VICE should be bounded by the named release or build, selected emulator and machine model, relevant resource settings, host operating context, and the supplied system and media files.

The dependency on system files is material to this boundary. The manual states that each emulator needs a system-ROM set; for C128 use it lists Kernal, BASIC-plus-Editor, and character-generator files, while hardware-level disk-drive emulation can require drive ROMs. This describes a configuration prerequisite, not permission to distribute ROMs, firmware, applications, or media images. VICE 3.10 release notes also record changes to device-related names, the monitor, and filesystem-device behavior, so a configuration report should not convert a version-specific observation into a timeless feature claim.

C128 context

The original C128 has C128, C64, and CP/M operating modes; the historical system guide associates CP/M mode with the onboard Z80 and with 40- or 80-column output. VICE documents its C128 emulator, x128, as providing internal-MMU emulation, an 80-column VDC screen, fast IEC, a 2 MHz mode, Z80 emulation, and C64-emulation features. Those documented facilities support a configured C128 application and test environment, but they do not establish that every result is identical to original hardware.

A C64Sets guide provides an independently authored practical example with an important date limit. Version 2.0 of that guide, dated 31 March 2024, says it was written and checked with VICE 3.7 and describes an x128 CP/M procedure using a boot disk on device 8 and an 80-column display choice. It is evidence of that VICE 3.7, 2024 workflow only; it does not demonstrate that every step, image, menu, or outcome remained unchanged in VICE 3.10. A useful C128 test record consequently names the selected mode, display path, ROM set, release, media, and drive configuration instead of reporting only that it ran under VICE.

Media, host filesystems, and sessions

VICE distinguishes host files from emulated media. Its manual documents attachable D64, G64, and P64 disk images and T64 and TAP tape images; it describes T64 support as limited and recommends TAP for actual tape emulation. Attachment state, image identity, write protection, and selected drive behavior are therefore part of a test condition rather than incidental details.

The manual describes filesystem-device settings for Commodore device numbers 8 through 11, while an independent C64 OS guide shows a host directory configured as a VICE filesystem device for transfer into an emulated environment. A host-directory mapping is useful for application work and development, but it changes the available inputs and should be recorded with the device number and any image attached to the same test. The invocation documentation also specifies disk-image attachments and read-only or read-write choices for devices 8 through 11, allowing a test report to identify media state without embedding the media file.

A snapshot saves complete emulator state and may restore saved memory configuration, which makes it useful for suspending or returning to a defined emulator session. VICE warns that module-version compatibility proved difficult to maintain and explicitly says snapshots should not be used for permanent or long-term storage. Event histories can retain interaction from an initial snapshot, yet the manual says playback can differ because of the snapshot or settings and that snapshots may not be fully accurate even with recommended settings. Repeatable testing therefore requires a pinned build, configuration, lawful ROM and media identifiers or hashes, host mappings, and read/write state; a snapshot or event history alone is neither a preservation object nor a universal reproducibility guarantee.

Drive behavior and development workflow

VICE describes true-drive emulation as slower hardware-level drive emulation for maximum compatibility, and it warns that an incorrect synchronization value can break operation or corrupt disk images. It also distinguishes true-drive settings from filesystem-device use, while the C64 OS guide separately demonstrates a virtual image drive and a host-filesystem device. Autostart can temporarily alter true-drive behavior under a stated setting, and VICE warns that this path is not completely safe in every case. A successful load is thus evidence about its declared configuration, not a universal statement about every disk, drive, host, or original peripheral.

VICE includes a monitor that can examine, disassemble, and assemble machine-language programs and debug through breakpoints. Its documented checkpoint types include tracepoints and watchpoints, and its state facilities include register inspection and instruction stepping. Independent Codebase64 guidance corroborates the monitor’s use for breakpoints, stepping, and labels in an iterative development workflow.

VICE also documents a binary remote monitor over a dedicated connection, and the 3.10 notes describe a new binary remote protocol and filesystem-device monitor actions. An earlier Codebase64 article demonstrates the general idea of a persistent remote-monitor development session driven from a shell, Makefile, or IDE, but it explicitly concerns an earlier SVN-build context rather than VICE 3.10. Monitor inspection and intervention should be distinguished in test notes, because loading data, changing a register, or changing a drive setting alters the session being examined.

Limits and preservation boundary

VICE describes an aim of cycle accuracy while cautioning that the C128 and several other emulators should not be expected to be as good as the C64 or VIC20. This qualification, together with the drive, event-history, snapshot, and version limits above, makes VICE valuable for bounded application use, debugging, and comparative testing but not proof of perfect compatibility, physical authenticity, or universal hardware behavior.

VICE is not a physical-media repair system or a preservation repository. The project directs original disk and tape transfer questions to separate tools such as OpenCBM and explains that a normal PC 5¼-inch drive cannot read C64 disks without suitable controller capability. Disk, tape, cartridge, ROM, and snapshot files need separate provenance, rights, and preservation decisions, and this article makes no claim about their legal availability or archival status.

See also

• Commodore 1541
• Commodore Datasette

Automation and sourcing note

This private candidate is original, citation-led prose about a version-scoped application, testing, and development environment. It republishes no manual prose, quotation, command block, source code, binary, ROM, firmware, disk, tape, cartridge, snapshot, image, screenshot, scan, database export, or media file; cited material remains citation-only evidence. It was not published and earns zero benchmark coverage credit unless a separate gatekeeper later authorizes a create-only release and verifies live content.