C64 Jiffydos

shift + run/stop

shift + run/stop loads and runs the first program on the disk automatically — no typing required at all. This works on stock ROMs but with JiffyDOS it benefits from the faster load speed.

7. Re-Enabling JiffyDOS (if it was disabled)

If the wedge gets disabled (via @q, or a program reset clears things):

Diagnosis flowchart:

1. User typed @ → ?SYNTAX ERROR? → Run sys 58451 first.
2. If that works, the wedge is back.
3. If that also gives a ?SYNTAX ERROR, JiffyDOS isn't loaded at all — check the emulator ROM configuration.
4. If @ works, try sys 58551 to restore function key macros.

8. Enabling JiffyDOS in Emulators

VICE (x64, x64sc, x128, etc.)

Kernal ROM:

• Settings → Cartridge/ROM settings → Kernal ROM → load a jiffydos_c64.rom file
• Or place the file in VICE's ROM directory and name it so VICE auto-loads it (consult VICE docs for your version)

Drive ROM (needed for fast loading):

• Settings → Drive Settings → Drive 8 ROM → load jiffydos_1541.rom
• Repeat for drive 9, drive 10, etc.
• JiffyDOS drive ROMs are needed for the ~10× speed increase. Without them, the Kernal wedge commands still work but loading is at normal speed.

Both Kernal and drive ROMs must be loaded for the full JiffyDOS experience. If only the Kernal ROM is loaded, you get the wedge commands (@, /, ↑, etc.) but still at stock speeds.

Ultimate 64 / Ultimate 64 Elite

• Access the Ultimate's firmware configuration menu
• JiffyDOS is built into the Ultimate firmware — no separate ROM file needed
• Enable JiffyDOS in the "ROM" or "C64 System" settings

9. Performance Characteristics

The speedup is because JiffyDOS uses a custom serial protocol that keeps the bus busy almost continuously, versus stock Commodore's "one byte, pause, next byte" approach.

Wedge commands work regardless of load speed — the @ commands and / shortcuts work with any drive. The speed boost only kicks in when both the computer and drive have JiffyDOS ROMs.

10. Compatibility Notes

What works with JiffyDOS

• All standard Commodore file types (PRG, SEQ, USR, REL)
• GEOS (auto-detected and given compatible timing)
• Most commercial software
• Multi-drive setups
• Files created under JiffyDOS are byte-identical to those from stock ROMs — fully portable

What doesn't work / workarounds

• Copy-protected software that relies on exact drive timing may fail. Use @q to disable the wedge and try again. If still fails, switch to stock Kernal ROM.
• Fastload cartridges (Action Replay, etc.) — JiffyDOS replaces the Kernal, so cartridges that also replace the Kernal conflict. Use one or the other.
• Custom Kernal patches — JiffyDOS replaces the entire Kernal, so other ROM patches won't survive.

Switching between JiffyDOS and stock

For a quick toggle in VICE:

• Soft toggle: @q disables wedge (can re-enable with sys 58451)
• Full ROM switch: Use VICE's Settings → Cartridge/ROM settings → Kernal ROM and start a new session

11. Typical Workflow Examples

Basic: "What's on the disk?"

Prompt: "I just booted my C64 emulator and want to see what's on the disk."

@$               ← displays directory without overwriting memory

Normal: "Load and run a game"

Prompt: "I want to load the file 'ASTROIDS' and run it."

@$               ← first check the directory to confirm the file exists
/astroids        ← (or if the filename is in uppercase: /ASTROIDS)
run              ← actually runs it
-- OR, in one step --
↑ASTROIDS        ← load and run in one

Advanced: "My disk has errors, help me fix it"

Prompt: "I tried loading something but got 'FILE NOT FOUND' even though the directory shows it."

1. @ — check the error channel. If it shows 26, write protect on or the directory was wrong, proceed.
2. @v — validate the disk (rebuilds BAM). This often fixes phantom errors.
3. @$ — check the directory again.
4. If the problem persists, ask "Has this disk been used on a non-JiffyDOS system? Files are compatible but the disk needs initialization."

Troubleshooting: "JiffyDOS commands don't work"

Prompt: "I typed @$ but got ?SYNTAX ERROR"

1. Check if JiffyDOS is actually loaded: ask the user about the boot screen message or to do a cold reset.
2. If it was loaded but got disabled: sys 58451 re-enables the wedge.
3. If sys 58451 also errors: JiffyDOS Kernal ROM isn't loaded. Guide them through VICE settings.
4. If the wedge works but loading is still slow: they need the drive ROM, not just the Kernal ROM.

12. Relationship to the c64-basic skill

When a conversation revolves around disk operations in an emulator context, this skill takes priority. When it revolves around writing new BASIC code, c64-basic takes priority. When the user is doing both, use both.

13. Quick Reference Card (most-used commands)

@           — Check disk error
@$          — List directory (safe for memory)
/name       — Load BASIC program
↑name       — Load and run BASIC program
←name       — Save BASIC program
%name       — Load ML program
@s:name     — Delete file
@r:new=old  — Rename file
@c:new=old  — Copy file on same disk
@n:disk,id  — Format disk (erases everything!)
@v          — Validate/repair disk
@i          — Reset drive
@o          — Un-new (recover BASIC after new)
sys 58451   — Re-enable wedge if disabled
shift+ro/st — Load+run first file on disk

14. Cross-references

• For writing Commodore 64 BASIC v2 programs (bc64 compiler, POKEs, sprites, SID, hardware control), see the c64-basic skill.
• For the Meatloaf full-mode HTTP client protocol and JSON Pointer syntax for API access, see the meatloaf-networking skill.
• For the unattended debug cycle (injecting BASIC, reading screen, capturing serial logs via Ultimate 64 REST API), see the c64-meatloaf-debug skill.