Commodore 64 ?CAN'T CONTINUE ERROR — How to Fix

What Does This Error Mean?

?CAN'T CONTINUE ERROR appears when you type CONT but BASIC can't resume the stopped program.
Either the program ended normally, the program text was edited after STOP, or something cleared the run state.
You can't 'undo' it — the only fix is to RUN the program from the start.
Save your code first if you've been editing.

Affected Models

Commodore 64
Commodore 64C
Commodore 128 in C64 mode
Commodore SX-64

Common Causes

Program already finished — no run to continue
You edited a line after STOP/END (any edit clears CONT)
Pressed RUN/STOP-RESTORE between STOP and CONT
First time you've typed CONT after a fresh load

How to Fix It

Decide whether the data in variables matters.

If the program just ended, variables are still in memory.
You can PRINT them or use the immediate mode to inspect values.
Type PRINT A or LIST to see code — but don't edit yet if you might want CONT.
Run from the start.

Type RUN and press RETURN.
The program restarts from line 0.
Any STOP/END the program hits next will allow CONT — provided you don't edit between.
Avoid the trap: don't edit after STOP.

Even retyping a line that's identical resets the CONT pointer.
If you want to continue after STOP, only inspect variables in immediate mode — don't change any program lines.

Frequently Asked Questions

Is there any way to truly resume after editing?

No — once you change a program line, BASIC discards the saved CONT pointer.
Variables stay in memory but execution can only start fresh.
This is by design and was the same on the VIC-20, PET, and Commodore 128.

What's the difference between CAN'T CONTINUE and BREAK?

BREAK appears when you press RUN/STOP and stops the program at a specific line.
CAN'T CONTINUE only appears when you try CONT after BASIC can no longer resume — often after BREAK plus an edit, or after the program ended normally.