Go to the first, previous, next, last section, table of contents.

3 Invoking the emulators

The names of the available emulators are:

You can run each of them by simply typing the name from a shell or by configuring your window manager for example to use them to open disk images.

If you want to look at the log output run them from a terminal window such as xterm or rxvt. For example, you could do

xterm -e x64sc

3.1 Command-line options used during initialization

There are several options you can specify on the command line. Some of them are used to specify emulation settings and will be described in detail later (see section 6 Settings and resources for a complete list). The remaining options are used only to give usage information or to initialize the emulator in some way:

List all the available command-line options and their meaning.
List all compile time features
Set default resources (see section 6 Settings and resources). This will override all the settings specified before, but not the settings specified afterwards on the command line.
-config <filename>
Specify config file
-dumpconfig <filename>
Write the complete config into file. Normally only resources that have been changed from their default value would be written to the config file, however with this option you can see all resources and their current values.
-logfile <name>
Specify log file name (LogFileName).
Enable verbose log output.
Disable all log output (except errors).
-keybuf <string>
Put the specified string into the keyboard buffer.
Console mode (for music playback, or for running the emulator test programs)
-limitcycles <cycles>
Automatically exit the emulator after a given number of cycles.
-chdir <directory>
Change the working directory.
-autostart <name>
Autostart <name> (see section 3.2 Autostarting programs from the command-line).
-autoload <name>
Attach and autoload tape/disk image <name>
-1 <Name>
Attach <Name> as a tape image file.
-8 <Name>
-9 <Name>
-10 <Name>
-11 <Name>
Attach <Name> as a disk image to device 8, 9, 10 or 11.
Attach disk image for drive #8-11 read only (AttachDevice8Readonly=1, AttachDevice9Readonly=1, AttachDevice10Readonly=1, AttachDevice11Readonly=1) (all emulators except vsid).
Attach disk image for drive #8-11 read write (if possible) (AttachDevice8Readonly=0, AttachDevice9Readonly=0, AttachDevice10Readonly=0, AttachDevice11Readonly=0) (all emulators except vsid).
-exitscreenshot <name>
Specify name of a screenshot file that will be written when the emulator exits. (ExitScreenshotName).
-exitscreenshotvicii <name>
Specify name of a screenshot file that will be written when the emulator exits. (ExitScreenshotName1). (x128)

3.2 Autostarting programs from the command-line

It is possible to let the emulator autostart a disk or tape image file, by simply specifying its name as the last argument on the command line, for example

x64sc lovelygame.d64

will start the C64 emulator, attaching `lovelygame.d64' as a disk image and running the first program on it. You can also specify the name of the program on the fisk image by appending a colon (`:') the name itself to the argument; for example

x64sc "lovelygame.d64:run me"

will run the program named `run me' on `lovelygame.d64' instead of the first one.

Using the command-line option -autostart is equivalent; so the same result can be obtained with

x64sc -autostart "lovelygame.d64:run me"

If you specify a raw CBM or P00 file, the emulator will setup the file system based drive emulation so that it is enabled and accesses the directory containing the file first. This is a very convenient way to start multi-file programs stored in file system directories and not requiring "true" drive emulation.

See section 5.5 Using disk and tape images. for more information about images and autostart.

Go to the first, previous, next, last section, table of contents.