This section lists the settings and commands that are C64/128 specific and thus are not present in the other emulators.
The cartridge system is organized in "Slots" to allow more than one cartridge connected at a time, like it can be done using an expansion port expander on a real C64 (see below).
Generally a cartridge can be enabled by attaching its respective cartridge image, or using the respective menu option for cartridges that do not require an image.
x64, x64sc and x128 allow you to attach the following kinds of images:
Cartridge images are like disk images, but contain the contents of cartridge ROM and/or RAM images instead of disk images.
To attach cartridges, use the "Attach a cartridge image" submenu. When using `.crt' images, this will work for every cartridge which is supported. For raw `.bin' images you might have to use command line options.
When you have successfully attached a cartridge image, you should then reset the machine to make sure the cartridge initializes itself. (Or enable the "reset on cartridge change" option).
Of course, it is also possible to detach a currently attached cartridge image ("Detach cartridge image").
If you are using a freezer cart like an Action Replay cartridge, you can emulate the cartridge's freeze button with the "Cartridge freeze" command.
The imaginary expansion port expander is organized in 4 slots, the cartridges are associated with them like this:
All carts that have a passthrough connector go here. Once a "Slot 0" cartridge is enabled all further cartridges are connected to its respective passthrough port.
Only one cartridge of this type can be active at a time.
"Slot 0" carts have individual "enable" switches, enabling means enabling permanently.
The following cartridges are emulated in this slot:
http://www.funet.fi/pub/cbm/schematics/cartridges/c64/ieee-488/eprom.bin
)
Mostly RAM based cartridges which for one reason or the other might make sense to be enabled together with one of the "Main Slot" cartridges go here.
Only one cartridge of this type can be active at a time.
"Slot 1" carts have individual "enable" switches, enabling means enabling permanently
The following cartridges are emulated in this slot:
All other cartridges which are not pure i/o extensions go here.
Only one cartridge of this type can be active at a time.
Cartridges in the "Main Slot" must be explicitly set as default to enable them permanently.
The following cartridges are emulated in this slot:
http://www.volny.cz/dundera/
)
All carts that are pure I/O extensions go here.
Any number of "I/O Slot" Carts may be active at a time.
"I/O Slot" carts have individual "enable" switches, enabling means enabling permanently.
The following cartridges are emulated in this slot:
When the emulator is run without arguments, all settings from the config file should be applied and arguments override settings from the config file.
When saving the settings to the config file it is expected that on the next run of the emulator all settings will be in the same state as they were when saved.
There is an exception to this rule: the cartridge in the "Main Slot" must be explicitly set as default before it gets saved to the config file.
+cart
should disable ALL cartridges, including eventually activated REU,
Swithlink and all similar expansionport devices.
-cartXYZ
options should generally attach AND activate a cart of type XYZ.
As a consequence, attaching carts this way which are NOT in the "Main Slot" will
also enable the cart permanently.
If attaching a cartridge does not work as expected, this may be because of various reasons:
.crt
files found "in the wild".
Make sure this is not the case (if in doubt use cartconv
to verify and/or fix).
+cart
on the command-line.
To be able to use an IEEE drive, you need to enable IEEE emulation for the emulator. To do this, follow the following steps:
Download the IEEE 488 ROM image from the CBM archives (formerly known as FUNET) Attach that image with File/Attach cartridge image/IEEE488 interface image.
Make sure you have a one-drive system only (that is, go to Settings/Peripheral Setting, uncheck "use IEC device" for all devices, go to Settings/Drive Settings and select "Floppy type" as "none" for all drives other than drive 8.
After this, all drives can be selected in x64 and x128.
The Final Cartridge 3 detects wether a mouse is connected when it starts and disables mouse support if it doesnt detect one. So to make mouse emulation work you must either enable it on the command line, or reset the cartridge after enabling it from the user interface.
CartridgeReset
CartridgeType
CartridgeFile
DQBB
DQBBfilename
DQBBImageWrite
ExpertCartridgeEnabled
Expertfilename
ExpertImageWrite
ExpertCartridgeMode
IDE64Image1
IDE64Image2
IDE64Image3
IDE64Image4
IDE64Config
IDE64Cylinders
IDE64Heads
IDE64Sectors
IDE64AutodetectSize
IDE64version4
IDE64RTCOffset
IEEE488
IEEE488Image
IsepicCartridgeEnabled
Isepicfilename
IsepicSwitch
IsepicImageWrite
MagicVoiceCartridgeEnabled
MagicVoiceImage
MMC64
MMC64BIOSfilename
MMC64_bios_write
MMC64_flashjumper
MMC64_revision
MMC64imagefilename
MMC64_RO
MMC64_sd_type
MMCRCardImage
MMCREEPROMImage
MMCRRescueMode
MMCRImageWrite
MMCRCardRW
MMCRSDType
MMCREEPROMRW
RAMCART
RAMCARTfilename
RAMCARTImageWrite
RAMCART_RO
RAMCARTsize
RRFlashJumper
RRBankJumper
RRBiosWrite
+cart
-cartreset
+cartreset
-cart8 <name>
-cart16 <name>
-cartultimax <name>
-cartcrt <name>
-cartap <name>
-cartar2 <name>
-cartar3 <name>
-cartar4 <name>
-cartar5 <name>
-cartcap <name>
-cartcomal <name>
-cartdep256 <name>
-cartdep64 <name>
-cartdep7x8 <name>
-cartdin <name>
-cartdsm <name>
-cartdqbb <name>
-dqbb
+dqbb
-dqbbimage <name>
-dqbbimagerw
+dqbbimagerw
-carteasy <name>
-easyflashjumper
+easyflashjumper
-easyflashcrtwrite
+easyflashcrtwrite
-cartepyx <name>
-cartexos <name>
-cartexpert <name>
-expert
+expert
-expertimagename <name>
-expertimagerw
+expertimagerw
-cartfc1 <name>
-cartfc3 <name>
-cartfcplus <name>
-cartff <name>
-cartfm <name>
-cartfp <name>
-cartgk <name>
-cartgs <name>
-cartide64 <name>
-IDE64image1 <name>
-IDE64image2 <name>
-IDE64image3 <name>
-IDE64image4 <name>
-IDE64cyl <value>
-IDE64hds <value>
-IDE64sec <value>
-IDE64autosize
+IDE64autosize
-IDE64version4
+IDE64version4
-cartieee <name>
-ieee488
+ieee488
IEEE488=1
) or disable (IEEE488=0
) emulation of the
IEEE488 interface.
-ieee488image <name>
-isepic
+isepic
-cartisepic <name>
-isepicimagename <name>
-isepicimagerw
+isepicimagerw
-cartkcs <name>
-cartmach5 <name>
-cartmd <name>
-cartmf <name>
-cartmikro <name>
-mmc64
+mmc64
-cartmmc64 <name>
-mmc64bios <name>
-mmc64image <name>
-mmc64readonly
-mmc64readwrite
-mmc64bioswrite
-cartmmcr <name>
-mmcrrescue
+mmcrrescue
-mmcrimagerw
+mmcrimagerw
-mmcrcardimage <filename>
-mmcrcardrw
+mmcrcardrw
-mmcreepromimage
-mmcreepromrw
+mmcreepromrw
-cartmv <name>
-cartocean <name>
-cartp64 <name>
-cartramcart <name>
-ramcart
+ramcart
-ramcartsize <size in KB>
-ramcartimage <name>
-ramcartimagerw
+ramcartimagerw
-cartrep256 <name>
-cartross <name>
-cartrr <name>
-rrbioswrite
+rrbioswrite
-rrbankjumper
+rrbankjumper
-rrflashjumper
+rrflashjumper
-cartru <name>
-carts64 <name>
-cartsb <name>
-cartse5 <name>
-cartsg <name>
-cartsimon <name>
-cartss4 <name>
-cartss5 <name>
-cartstar <name>
-cartwl <name>
-cartws <name>
-cartzaxxon <name>
-ciamodel <model>
-cia1model <model>
-cia2model <model>
These settings control the emulation of the VIC-II (MOS6569) video chip used in both the C64 and the C128.
VICIICheckSsColl
VICIICheckSbColl
VICIIVideoCache
VICIIDoubleSize
VICIIDoubleScan
VICIIPaletteFile
-VICIIcheckss
+VICIIcheckss
VICIICheckSsColl=1
) and disable (VICIICheckSsColl=0
)
emulation of hardware sprite-sprite collision detection, respectively.
-VICIIchecksb
+VICIIchecksb
VICIICheckSbColl=1
) and disable (VICIICheckSbColl=0
)
emulation of hardware sprite-background collision detection,
respectively.
-VICIIvcache
+VICIIvcache
VICIIVideoCache=1
, VICIIVideoCache=0
).
-VICIIdsize
+VICIIdsize
VICIIDoubleSize=1
,
VICIIDoubleSize=0
).
-VICIIdscan
+VICIIdscan
VICIIDoubleScan=1
,
VICIIDoubleScan=0
).
-VICIIhwscale
+VICIIhwscale
-VICIIscale2x
+VICIIscale2x
-VICIIintpal
-VICIIextpal
-VICIIpalette NAME
NAME
as the palette file (VICIIPaletteFile
).
-VICIIfulldevice <device>
-VICIIXRANDRfullmode <mode>
-VICIIVidmodefullmode <mode>
-VICIIborders <mode>
-VICIImodel <model>
x64sc
.
-newluminance
+newluminance
-saturation <0-2000>
-contrast <0-2000>
-brightness <0-2000>
-gamma <0-4000>
-tint <0-2000>
-oddlinesphase <0-2000>
-oddlinesoffset <0-2000>
-crtblur <0-1000>
-crtscanlineshade <0-1000>
These settings control the emulation of the SID (MOS6581 or MOS8580) audio chip.
SidStereo
SidStereoAddressStart
SidFilters
SidModel
0
:
MOS6581, 1
: MOS8580).
SidEngine
SidResidSampling
0
: Fast, 1
:
Interpolation, 2
: Resampling)
SidResidPassband
0 - 90
).
-sidstereo
SidStereo
).
-sidstereoaddress ADDRESS
SidStereoAddressStart
).
-sidenginemodel <engine and model>
SID engine
and MODEL
for the emulated SID chip (
0: FastSID 6581,
1: FastSID 8580,
256: ReSID 6581,
257: ReSID 8580,
258: ReSID 8580 + digiboost,
1024: ParSID in par port 1,
1280: ParSID in par port 2,
1536: ParSID in par port 3,
1800: ReSID-FP 6581R3 4885,
1801: ReSID-FP 6581R3 0486S,
1802: ReSID-FP 6581R3 3984,
1803: ReSID-FP 6581R4 AR 3789,
1804: ReSID-FP 6581R3 4485,
1805: ReSID-FP 6581R4 1986S,
1808: ReSID-FP 8580R5 3691,
1809: ReSID-FP 8580R5 3691 + digiboost,
1810: ReSID-FP 8580R5 1489,
1811: ReSID-FP 8580R5 1489D).
-sidfilters
+sidfilters
SidFilters=1
) or disable (SidFilters=0
) emulation
of the built-in SID filters.
-residsamp METHOD
SidResidSampling=0
),
interpolating (SidResidSampling=1
), resampling
(SidResidSampling=2
), fast resampling (SidResidSampling=3
).
-residpass PERCENTAGE
SidResidPassband=0-90
).
-residgain PERCENTAGE
-residfilterbias <number>
I/O extensions are (usually) cartridges which do not map into ROM space, but use only the I/O space at address range $DE00 ... $DEFF and/or $DF00 ... $DFFF.
Please use these extensions only when needed, as they might cause compatibility problems.
The following I/O extensions are available:
TODO
Acia1Enable
DIGIMAX
DIGIMAXbase
ETHERNET_INTERFACE
ETHERNET_DISABLED
ETHERNET_ACTIVE
ETHERNET_AS_RR
GEORAM
GEORAMfilename
GEORAMImageWrite
GEORAMsize
MIDIEnable
MIDIMode
REU
REUfilename
REUImageWrite
REUsize
SFXSoundExpander
SFXSoundExpanderChip
SFXSoundSampler
-acia1
+acia1
-digimax
+digimax
-digimaxbase <base address>
-miditype <0-4>
-midi
+midi
-midiin <name>
-midiout <name>
-mididrv <driver>
-georam
+georam
-cartgeoram <name>
-georamimage <name>
-georamimagerw
+georamimagerw
-georamsize <size in KB>
-reu
+reu
REU=1
) or disable (REU=0
) emulation of the
RAM Expansion Module.
-cartreu <name>
-reuimage <name>
-reuimagerw
+reuimagerw
-reusize <size in KB>
-sfxse
+sfxse
-sfxsetype <type>
-sfxss
+sfxss
-tfe
+tfe
-tfeif <name>
-tferrnet
+tferrnet
These settings can be used to control what system ROMs are loaded in the C64/128 emulators at startup. They cannot be changed from the menus.
KernalName
BasicName
ChargenName
KernalRev
0
3
sx
67
100
4064
-kernal NAME
KernalName
).
-basic NAME
BasicName
).
-chargen NAME
ChargenName
).
-kernalrev REVISION
KernalRev
).
-gluelogictype <type>
-plus60k
+plus60k
-plus60kimage <name>
-plus60kbase <base address>
-plus256k
+plus256k
-plus256kimage <name>
-256k
+256k
-256kimage <name>
-256kbase <base address>
-VDCvcache
+VDCvcache
-VDCdsize
+VDCdsize
-VDCdscan
+VDCdscan
-VDChwscale
+VDChwscale
-VDCintpal
-VDCextpal
-VDCpalette <name>
-VDCfulldevice <device>
-VDCXRANDRfullmode <mode>
-VDCVidmodefullmode <mode>
-VDC16KB
-VDC64KB
-VDCRevision <number>
-saturation <0-2000>
-contrast <0-2000>
-brightness <0-2000>
-gamma <0-4000>
-tint <0-2000>
-oddlinesphase <0-2000>
-oddlinesoffset <0-2000>
-crtblur <0-1000>
-crtscanlineshade <0-1000>
-basic64 <name>
-kernal64 <name>
-basiclo <name>
-basichi <name>
-kernal <name>
-kernalde <name>
-kernalfi <name>
-kernalfr <name>
-kernalit <name>
-kernalno <name>
-kernalse <name>
-chargen <name>
-chargde <name>
-chargfr <name>
-chargse <name>
-intfunc
+intfunc
-intfrom <name>
-extfunc
+extfunc
-extfrom <name>
-40col
-80col
-go64
+go64
This section lists the settings and commands that are C64DTV specific and thus are not present in the other emulators.
The DTV has a 2MB Flash chip which contains the kernal, basic and character set ROMs along with other data, such as games in the case of the original C64DTV ROM.
The image file is a dump of the flash chip. It is exactly 2MB (2097152 bytes).
If you do not have a suitable image file, an image using the C64 kernal, basic and charset is automatically created.
If writing to the C64DTV ROM is enabled, the image file is rewritten with the current data when exiting x64dtv.
Note that x64dtv tries to load the image file from the C64DTV directory first, and if it isn't found there, x64dtv tries to load it from the current directory. If you do not have `dtvrom.bin' in your C64DTV directory and writing to DTV ROM is enabled, the `dtvrom.bin' file is created to the current directory.
NOTE: The original C64DTV ROM has somewhat distorted colors, normally you should use a patched rom.
-c64dtvromimage NAME
-c64dtvromrw
+c64dtvromrw
The trueflashfs option is analogous to True drive emulation. If disabled, any file access to the flash filesystem (device 1) will go to the local file system instead.
-trueflashfs
+trueflashfs
-fsflash NAME
The DTV revision 2 has a bug in the Blitter. Using revision 3 is recommended. Emulation of DTV revision 2 including Blitter bug is intended for testing DTV software.
-dtvrev REVISION
The PAL C64DTVs have wrong resistors in the video output circuit, which causes incorrect luminances. Several hardware solutions ("LumaFixes") have been developed to fix this flaw.
The fixed video output is emulated by selecting "New Luminances". The unmodified C64DTV video output can be emulated with "Old Luminances".
The default setting is "New Luminances".
The C64DTV userport emulation currently supports three devices: Hummer ADC, userport joystick and PS/2 mouse.
The joystick that controls either the Hummer ADC or userport joystick can be selected using the same parameter or menu option.
While using the Hummer ADC, joystick UP and DOWN are mapped to the Hummer buttons A and B respectively. LEFT and RIGHT set the ADCs output to 0 and 255. Centering the joystick results in the ADC value of 128.
Currently the Hummer ADC and userport joystick are mutually exclusive. This means that enabling one disables the other. PS/2 mouse emulation can be used simultaneously with either Hummer ADC or userport joystick.
-hummeradc
+hummeradc
-ps2mouse
+ps2mouse
Debugging information on Blitter, DMA and Flash can be enabled with command line parameters. This can be useful for DTV software development.
-dtvblitterlog
+dtvblitterlog
-dtvdmalog
+dtvdmalog
-dtvflashlog
+dtvflashlog
Currently the registers A, Y and X are registers R0, R1 and R2 regardless of the mapping, which can be seen and modified via the registers ACM and XYM.
The monitor can access all 2MB of RAM and 2MB of Flash, but only 64 kB at a time. The 64kB bank can be selected with "bank ram00".."ram1f" for RAM and "bank rom00".."rom1f" for Flash.
The "load" command can load large files (>64kB) correctly if the bank is set to "ramXX", where XX is the starting bank (usually "bank00").
This section lists the settings and commands that are VIC20-specific and thus are not present in the other emulators.
As with the C64 (see section 7.1.1 Using cartridges), it is possible to attach several types of cartridge images:
This can all be done via the "Attach cartridge image..." command in the left-button menu. It is also possible to let xvic "guess" the type of cartridge using "Smart-attach cartridge image...".
Notice that several cartridges are actually made up of two pieces (and two files), that need to be loaded separately at different addresses. In that case, you have to know the addresses (which are usually specified in the file name) and use the "attach" command twice.
A special kind of cartridge file is where the two files mentioned above are concatenated (with removing the two byte load address of the second image) into one 16k image. There are only few of those images, though. Normally the second part is located at $A000. Vice can now attach such concatenated files at the start address $2000, $4000, and $6000. The second half of such an image is moved to $A000. If you encounter 16k images that have the second half not at $A000 you can split the image into two halfs (i.e. one 8194 byte and one 8192 byte, because the first has the load address) and attach both files separately.
One cartridge that is currently only partially supported here is the VIC1112 IEEE488 interface. You have to load the ROM as a cartridge, but you also have to enable the IEEE488 hardware by menu.
-cart2 <name>
-cart4 <name>
-cart6 <name>
-cartA <name>
-cartB <name>
-cartgeneric <name>
-cartmega <name>
-mcnvramfile <name>
-mcnvramwriteback
+mcnvramwriteback
-cartfe <name>
-fewriteback
+fewriteback
-cartfp <name>
-fpwriteback
+fpwriteback
-ieee488
+ieee488
-sidcart
+sidcart
VICVideoCache
VICDoubleSize
VICDoubleScan
VICPaletteFile
-VICvcache
+VICvcache
VICVideoCache=1
, VICVideoCache=0
).
-VICdsize
+VICdsize
VICDoubleSize=1
,
VICDoubleSize=0
).
-VICdscan
+VICdscan
VICDoubleScan=1
,
VICDoubleScan=0
).
-VIChwscale
+VIChwscale
-VICscale2x
+VICscale2x
-VICpalette NAME
NAME
as the palette file (VICPaletteFile
).
-VICintpal
-VICextpal
-VICfulldevice <device>
-VICXRANDRfullmode <mode>
-VICVidmodefullmode <mode>
-saturation <0-2000>
-contrast <0-2000>
-brightness <0-2000>
-gamma <0-4000>
-tint <0-2000>
-oddlinesphase <0-2000>
-oddlinesoffset <0-2000>
-crtblur <0-1000>
-crtscanlineshade <0-1000>
It is possible to change the VIC20 memory configuration in two ways: by enabling and/or disabling certain individual memory blocks, or by choosing one among a few typical memory configurations. The former can be done by modifying resource values directly or from the right-button menu; the latter can only be done from the menu.
There are 5 RAM expansion blocks in the VIC20, numbered 0, 1, 2, 3 and 5:
These blocks are called expansion blocks because they are not
present a stock ("unexpanded") machine. Each of them is associated to
a boolean RamBlockX
resource (where X
is the block number)
that specifies whether the block is enabled or not.
There are also some common memory configurations you can pick from the right-button menu:
RAMBlock0
RAMBlock1
RAMBlock2
RAMBlock3
RAMBlock5
-memory CONFIG
none
(no extension);
all
(all blocks);
3k
(3k space in block 0);
8k
(first 8k extension block);
16k
(first and second 8k extension blocks);
24k
(first, second and 3rd extension blocks);
0
, 1
, 2
, 3
, 5
(memory in respective
blocks);
04
, 20
, 40
, 60
, A0
(memory at
respective address.
xvic -memory nonegives an unexpanded VIC20. While
xvic -memory 60,a0or
xvic -memory 3,5enables memory in blocks 3 and 5, which is the usual configuration for 16k ROM modules.
These settings can be used to control what system ROMs are loaded in the VIC20 emulator at startup. They cannot be changed from the menus.
KernalName
BasicName
ChargenName
GenericCartridgeFile2000
GenericCartridgeFile4000
GenericCartridgeFile6000
GenericCartridgeFileA000
GenericCartridgeFileB000
-kernal NAME
KernalName
).
-basic NAME
BasicName
).
-chargen NAME
ChargenName
).
-cart2 NAME
-cart4 NAME
-cart6 NAME
-cartA NAME
-cartB NAME
CartridgeFile2000
,...,CartridgeFileB000
).
-OEMjoy
+OEMjoy
-TEDvcache
+TEDvcache
-TEDdsize
+TEDdsize
-TEDdscan
+TEDdscan
-TEDscale2x
+TEDscale2x
-TEDhwscale
+TEDhwscale
-TEDintpal
-TEDextpal
-TEDpalette <name>
-TEDfulldevice <device>
-TEDXRANDRfullmode <mode>
-TEDVidmodefullmode <mode>
-saturation <0-2000>
-contrast <0-2000>
-brightness <0-2000>
-gamma <0-4000>
-tint <0-2000>
-oddlinesphase <0-2000>
-oddlinesoffset <0-2000>
-crtblur <0-1000>
-crtscanlineshade <0-1000>
-digiblaster
+digiblaster
-sidcart
+sidcart
-sidcartjoy
+sidcartjoy
-speech
+speech
-speechrom <name>
-functionlo <name>
-functionhi <name>
-c1lo <name>
-c1hi <name>
-c2lo <name>
-c2hi <name>
-ramsize <ramsize>
-h256k
-h1024k
-h4096k
-cs256k
This section lists the settings and commands that are PET-specific and thus are not present in the other emulators.
With xpet
, it is possible to change at runtime the
characteristics of the emulated PET so that it matches (or not) the ones
of a certain PET model, and it is also possible to select from a common
set of PET models so that all the features are selected accordingly.
The former is done by changing the following resources (via resource file, command line options or right-menu items):
RamSize
IOSize
VideoSize
Ram9
RamA
SuperPET
Basic1
Basic1Chars
EoiBlank
DiagPin
ChargenName
KernalName
EditorName
RomModule9Name
RomModuleAName
RomModuleBName
Choosing a common PET model is done from the right-button menu instead, by choosing an item from the "Model defaults" submenu. Available models are:
Notice that this will reset the emulated machine.
It is also possible to select the PET model at startup, with the
-model
command-line option: for example, `xpet -model 3032'
will emulate a PET 3032 while `xpet -model 8296' will emulate a PET
8296.
Crtc
CrtcVideoCache
CrtcDoubleSize
CrtcDoubleScan
CrtcPaletteFile
-Crtcvcache
+Crtcvcache
-Crtcdsize
+Crtcdsize
-Crtcdscan
+Crtcdscan
-Crtcscale2x
+Crtcscale2x
-Crtchwscale
+Crtchwscale
-Crtcintpal
-Crtcextpal
-Crtcpalette NAME
NAME
as the palette file (CrtcPaletteFile
).
-Crtcfulldevice <device>
-CrtcXRANDRfullmode <mode>
-CrtcVidmodefullmode <mode>
-saturation <0-2000>
-contrast <0-2000>
-brightness <0-2000>
-gamma <0-4000>
-tint <0-2000>
-oddlinesphase <0-2000>
-oddlinesoffset <0-2000>
-crtblur <0-1000>
-crtscanlineshade <0-1000>
It is possible to enable or disable emulation of the PET diagnostic pin
via the DiagPin
resource, or the "PET userport diagnostic pin"
item in the right-button menu.
When the diagnostic pin is set, the Kernal does not try to initialize the BASIC, but directly jumps into the builtin machine monitor.
These are the commandline options specific for the CBM-II models.
-model MODEL
-kernal NAME
KernalName
).
-editor NAME
EditorName
).
-chargen NAME
ChargenName
).
-rom9 NAME, -romA NAME, -romB NAME
RomModule9Name
, RomModuleAName
,
RomModuleBName
).
-petram9, +petram9
Ram9
).
-petramA, +petramA
RamA
).
-superpet, +superpet
SuperPET
).
-basic1, +basic1
Basic1
).
-basic1char, +basic1char
Basic1Chars
).
-eoiblank, +eoiblank
EoiBlank
).
-diagpin
+diagpin
DiagPin=1
) or disable (DiagPin=0
) the
diagnostic pin at the PET userport.
-petreu
+petreu
-petreuimage <name>
-petreuramsize <size in KB>
-userportdac, +userportdac
-petdww
+petdww
-petdwwimage <name>
-sidcart
+sidcart
It is also possible to choose what color set is used for the emulation
window. This is done by specifying a palette file name (see section 4.3 Palette files) in the PaletteName
resource. The menu provides the
following values:
green.vpl
(default, "green)"), the good old green-on-black
feeling;
amber.vpl
("amber"), an amber phosphor lookalike;
white.vpl
("white"), simple white-on-black palette.
This section lists the settings and commands that are CBM-II-specific and thus are not present in the other emulators.
With xcbm2
, it is possible to change at runtime the
characteristics of the emulated CBM so that it matches (or not) the ones
of a certain CBM model, and it is also possible to select from a common
set of CBM models so that all the features are selected accordingly.
The former is done by changing the following resources (via resource file, command line options or right-menu items):
UseVicII
RamSize
Ram08, Ram1, Ram2, Ram4, Ram6, RamC
Cart2Name, Cart4Name, Cart6Name
ModelLine
Choosing a common CBM-II model is done from the right-button menu instead, by choosing an item from the "Model defaults" submenu. Available models are:
Notice that this will reset the emulated machine.
Warning: At this time switching between 510 and other machines during runtime is not supported and will not work.
It is also possible to select the CBM model at startup, with the
-model
command-line option: for example, `xcbm2 -model 610'
will emulate a CBM 610 while `xcbm2 -model 620' will emulate a CBM
620. Notably this is the only way to start a C510 emulation, with
-model 510
.
These are the commandline options specific for the CBM-II models.
-ramsize <ramsize>
-usevicii
+usevicii
-kernal NAME
KernalName
).
-basic NAME
BasicName
).
-chargen NAME
ChargenName
).
-cart1 <name>
Cart1Name
).
-cart2 <name>
Cart2Name
).
-cart4 <name>
Cart4Name
).
-cart6 <name>
Cart6Name
).
-ram08
+ram08
Ram08
).
-ram1
+ram1
Ram1
).
-ram2
+ram2
Ram2
).
-ram4
+ram4
Ram4
).
-ram6
+ram6
Ram6
).
-ramC
+ramC
RamC
).
-modelline
It is also possible to choose what color set is used for the emulation
window. This is done by specifying a palette file name (see section 4.3 Palette files) in the PaletteName
resource. The menu provides the
following values:
green.vpl
(default, "green"), the good old green-on-black
feeling;
amber.vpl
("amber"), an amber phosphor lookalike;
white.vpl
("white"), simple white-on-black palette.
-vsid
x64
only).
-keepenv
-tune <number>
Go to the first, previous, next, last section, table of contents.