C128 keyboard unresponsive after exiting monitor
9 views
Skip to first unread message
John Watson
Mar 29, 2026, 6:23:13 PMMar 29
to id...@googlegroups.com
Hi all, hope I didn't wake you guys up ;)
I've just dug out my IDE64 after a while in hibernation. I tried
plugging it into my C64 Reloaded but kept getting the RAM message on
boot. I tried changing the PLA and cleaning the IDE64 contacts but still
no joy.
I then tried in my C128CR (flat). This worked fine. However each time I
start the monitor with C= RESTORE, type in a few commands, then exit
with Q, my keyboard doesn't appear to work. Each time I press a key the
cursor blinks rapidly but nothing ever appears on the screen. I have to
press the reset button to restore normal service.
Does anyone have any suggestions as to what might be happening here?
I've just dug out my IDE64 after a while in hibernation. I tried
plugging it into my C64 Reloaded but kept getting the RAM message on
boot. I tried changing the PLA and cleaning the IDE64 contacts but still
no joy.
I then tried in my C128CR (flat). This worked fine. However each time I
start the monitor with C= RESTORE, type in a few commands, then exit
with Q, my keyboard doesn't appear to work. Each time I press a key the
cursor blinks rapidly but nothing ever appears on the screen. I have to
press the reset button to restore normal service.
Does anyone have any suggestions as to what might be happening here?
John Watson
Mar 29, 2026, 6:35:49 PMMar 29
to id...@googlegroups.com
Just to add to this. If I start the monitor with SYS0 then press Q, I
can't type anything on the screen - there is no cursor.
Also, pressing HELP on the C128 keyboard doesn't start the monitor (as
stated in the manual).
> --
> You received this message because you are subscribed to the Google Groups "IDE64" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to ide64+un...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/ide64/239e4b8a-b9e0-4b08-82e8-a346f782a4e1%40proton.me.
can't type anything on the screen - there is no cursor.
Also, pressing HELP on the C128 keyboard doesn't start the monitor (as
stated in the manual).
> You received this message because you are subscribed to the Google Groups "IDE64" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to ide64+un...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/ide64/239e4b8a-b9e0-4b08-82e8-a346f782a4e1%40proton.me.
jo...@post.cz
Mar 30, 2026, 6:22:36 AMMar 30
to id...@googlegroups.com
I’ll investigate this further.
After Q, you can restore to a responsive state by pressing RUN/STOP + RESTORE.
Out of curiosity - what’s your use case for preferring Q over X?
After Q, you can restore to a responsive state by pressing RUN/STOP + RESTORE.
Out of curiosity - what’s your use case for preferring Q over X?
To view this discussion visit https://groups.google.com/d/msgid/ide64/96ab36eb-ec67-47b1-95ee-0e1a5ced1aa8%40proton.me.
John Watson
Mar 30, 2026, 12:00:52 PMMar 30
to id...@googlegroups.com
I got the C128 HELP key to work by setting it up in the Setup Utility
(left-arrow and RESTORE).
Regarding why Q instead of X... I honestly didn't see the option to use
X while reading the manual. Using X to exit works perfectly BTW.
However if I exit with Q (nothing appears on screen when typing), then
return to the monitor (either HELP or C= RESTORE), then exit the monitor
again with X, I still get the symptoms like I had used Q. Hope that is
clear. Seems like Q has some effect that latches. RUN/STOP + RESTORE
does indeed restore normal working.
(left-arrow and RESTORE).
Regarding why Q instead of X... I honestly didn't see the option to use
X while reading the manual. Using X to exit works perfectly BTW.
However if I exit with Q (nothing appears on screen when typing), then
return to the monitor (either HELP or C= RESTORE), then exit the monitor
again with X, I still get the symptoms like I had used Q. Hope that is
clear. Seems like Q has some effect that latches. RUN/STOP + RESTORE
does indeed restore normal working.
Reply all
Reply to author
Forward
0 new messages