|

Usage
ec64 runs on console only. Some seconds
after starting it the blue C64 screen should appear. Now you are in
"Keyboard mode" this means (nearly) all pressed keys will be
mapped to the C64 keyboard. Here some special keys (all other keys can
be examined through testing ;-):
PC Keyboard | C64 Keyboard
------------------------+------------------------
Shift Left | SHIFT Left
Shift Right | SHIFT Right
Ctrl Left, Ctrl Right | CONTROL
Alt | C=
TAB | RUNSTOP
Pause | RESTORE
|
The following keys have a special meaning to the emulator itself:
- Ctrl+ESC quits ec64
- F9 switches between the input modes: Keyboard, Joystick 1,
Joystick 2, Monitor
- F10 makes the Statusline always visible
- F11 makes the Monitor always visible (in large resolutions this is always the case)
- F12 takes a screenshot, if this feature was compiled in ec64
In "Joystick mode" only SPACE and the Cursorkeys are used
to emulate a joystick on Port 1 or 2
Monitor Commands
In "Monitor mode" you are able to manipulate the emulation.
The breakpoint commands are not very useful yet, so i don't explain
very much details about them.
- version
- displays the ec64 version
- load <d64|g64> <filename>
- loads a D64 disk image in the C1541 drive (G64 not supported
at the moment).
- save <d64|g64> <filename>
- saves the D64 disk image currently in the C1541 drive (G64 not
supported at the moment).
NOTE: If you have no disk image loaded the C1541 drive
contains an unformatted disk, this means you can't extract a
D64 image.
- cycles
- displays the emulated cycles
- stop
- stops the emulation
- continue
- continues the emulation
- reset <soft|hard>
- resets the emulation. Soft means a warmstart and hard a cold start
- sync <on|off>
- If sync is off the emulation runs at full host CPU speed. If
sync is on the emulation runs as fast as the original C64 (maybe
slower if your system is too slow)
- script <filename>
- all commands you can enter in the monitor, can also be loaded
as a script.
NOTE: you can produce endless loops if a script file
executes itself via the script command
- type <text>
- types something on the C64 keyboard, this is useful for
scripting. Special characters are excaped through a ^.
If keys should be pressed at once (for example RUNSTOP and RESTORE),
they have to be surrounded by `.
^l SHIFT Left
^r SHIFT Right
^c CONTROL
^o C=
^1 F1
^2 F2
^3 F3
^4 F4
^5 F5
^6 F6
^7 F7
^8 F8
^L (<=)
^E (L)
^H HOME
^I INST
^U (^)
^T RESTORE
^S RUNSTOP
^N RETURN
^D CURSOR DOWN
^R CURSOR RIGHT
|
Examples:
- type hello
- type \ world ; if your text contains
spaces you have to add a leading \
- type \10 print"hello world"^N20 goto 10^Nrun^Ndummy^Sdummy`^S^T`
; test it and you will see what happens :-)
- wait <number of frames>
- waits the given number of frames (useful for scripts)
- bpadd <modulid> <bptype> <bpflags> [start_address [end_address [value [mask]]]]
- add a breakpoint. Available modulid's are: c64cpu c1541cpu.
bptyte's: ro, rd, rs, wd, ws. Can also be written as
read_opcode, read_data, read_stack, write_data, write_stack.
Examples:
- bpadd c64cpu ro +trap 1000 1fff
- bplist <modulid> <bptype>
- lists the breakpoints for modulid and bptype
- bpdel <modulid> <bptype> <bpnumber>
- deletes a breakpoint
- exit
- quits ec64
- quit
- quits ec64
- help
- shows all available commands
Commandline Options
-f fullscreen 400x300@60Hz on fb device
(MAY BE NOT SUPPORTED ON ALL DEVICES!)
-s <file> load and execute script on startup
-d <file> load d64 file on startup
-dsp <file> audio device file
-fb <file> fb device file
|
Notes
- ec64 uses some sort of "quick hack" to block all gpm activity, this
works fine on my machine, but this may (or hopefully may not) cause
problems with different versions of gpm.
- ec64 runs slower under Mode X than with the fb device, especially
while massive screen changes and sprite movement.
- if the emulation seems to hang, probably a C64 program used some
features which are not implemented at the moment. If something
strange happens the emulation will be stopped and you get a message
to the monitor.
|
|