- Home
- Commodore 64 Emulators
- C64net
On the recordRead 8 Oct 202618 facts
C64net
On the record
- Audio limit
- SID chip emulation is not implemented.github.com · read 8 Oct 2026
- Compatibility limits
- Only documented CPU opcodes are implemented, and executing an undocumented opcode causes the emulator to crash.github.com · read 8 Oct 2026
- Disk images
- D64 is the only disk-image format implemented, and D64 extensions for bad-sector emulation are unsupported.github.com · read 8 Oct 2026
- Drive emulation
- It emulates a 1541-II disk drive at the hardware level, which uses more resources but improves compatibility.github.com · read 8 Oct 2026
- Emulation timing
- The emulator uses cycle-based emulation to synchronize chips and emulate their timing.github.com · read 8 Oct 2026
- Graphics
- It emulates the VIC-II graphics chip, including graphic modes, sprites, and collision detection.github.com · read 8 Oct 2026
- Hardware coverage
- The implementation covers much of the hardware needed to run games, including the VIC-II graphics chip and keyboard and joystick input.github.com · read 8 Oct 2026
- Input
- The implementation includes keyboard and joystick emulation.github.com · read 8 Oct 2026
- License
- The repository identifies its license as GPL-3.0.github.com · read 8 Oct 2026
- Missing features
- SID sound-chip emulation, REU emulation, and tape emulation are unavailable.github.com · read 8 Oct 2026
- Other limits
- REU and tape emulation are unavailable, and only documented CPU opcodes are implemented.github.com · read 8 Oct 2026
- Product
- C64net is a Commodore 64 emulator written in C#.github.com · read 8 Oct 2026
- Project status
- The maker says this C# implementation was abandoned after a C++ reimplementation and describes it as a base for explaining emulation.github.com · read 8 Oct 2026
- Purpose
- C64net is a Commodore 64 emulator written in C#.github.com · read 8 Oct 2026
- ROM files
- ROM files are excluded for legal reasons and must be obtained separately and placed in the project ROM folder or beside the executable.github.com · read 8 Oct 2026
- ROM requirement
- ROM files are excluded for legal reasons and must be obtained separately and copied into the project ROM folder or alongside the executables.github.com · read 8 Oct 2026
- Save states
- Emulator state can be saved or loaded, with saves written only at the end of a frame.github.com · read 8 Oct 2026
- Timing
- The emulator uses cycle-based timing to synchronize chips and implements real-drive emulation of a 1541-II disk drive.github.com · read 8 Oct 2026