Skip to content

CSL Scripts

WacKEDmaN edited this page Oct 31, 2026 · 1 revision

CSL scripts

CSL (CPC Script Language) 1.5 and SSM (ScreenShot Management) 1.1 are standards by Longshot. A CSL script sets up a machine, inserts media, types keys, waits and takes screenshots. The SHAKER test suite uses them.

From the window

Tools → CSL scripts (or File → Run CSL script...):

Setting What it is
Script The .csl file (Browse...)
Screenshots The folder for the screenshots, snapshots and the log
Disc folder The folder for the disc images that the script names
CRTC As the script says, or a CRTC type for each crtc_select
Follow csl_load chains Run the scripts that a script loads with csl_load
Apply published-script errata Off: play published scripts exactly as written (below)

Run starts the script in a separate run with no window; Stop ends it. Open screenshot folder shows the results. The window shows the command line that does the same.

From the command line

cpcse --csl SHAKE27A-1.CSL --out shots --disk-dir <folder with shaker27.dsk>
Option What it does
--csl <file> The script to play (starts this mode)
--out <dir> The folder for screenshots, snapshots and csl.log (default screenshots)
--roms <dir> The firmware and the Plus system cartridge (default roms)
--disk-dir <dir>, --tape-dir <dir> The folders for the media that a script names
--model <id> The machine for a script with no cpc_model (default cpc6128)
--crtc <n> Use this CRTC type (0 to 4) for each crtc_select
--emu-name <name> The prefix of the image names (default CPCSE)
--csl-log <file> The log of the run (default <out>/csl.log)
--no-chain Do not follow csl_load
--no-errata Run published scripts exactly as written

What the player knows

All the CSL 1.5 instructions:

  • wait_ssm 0xHHHH: the script waits until the program sends that SSM code and its screenshot is saved.
  • Machine configuration: cpc_model, crtc_select (0, 1, 1A, 1B, 2, 3, 4), gate_array, memory_exp, rom_dir, rom_config.
  • reset soft and reset hard.
  • Disc, tape and snapshot media, and their folders.
  • Keys: \(...) codes, {groups}, \(KOF), key_from_file, keyboard_write.
  • The four wait instructions.
  • Screenshots and snapshots (versions 1 to 3), with their names and folders.
  • csl_load.

SSM screenshots

The emulated program asks for a screenshot with an SSM code: the Z80 bytes ED LL ED HH. The emulator saves each one as CPCSE_<crtc>_<HHLL>.bmp, the name format that the SSM standard gives for the SHAKER portal.

  • SSM #0000 ends a wait_ssm0000.
  • #FFFE saves the named screenshot; #FFFF saves a snapshot.
  • crtc_select 3 with no model makes a 6128 Plus, because CRTC 3 is its ASIC.
  • The player goes from the Plus menu to BASIC before the script starts.

If the machine cannot do an instruction, the script stops with the report that the standard gives: the script, the line, the instruction, the reason, the CSL version of the script and the supported version.

Erratum

SHAKER 2.7 added a ninth sub-test ("R4 & R9 check") to its test U. The SHAKE27A-*.CSL scripts do not include this change. The test now ends 14.2 s to 14.7 s after its key, but the script continues after 14 s, so it does not get to the next five screens. The player makes that one wait 16 s and writes this in the log. --no-errata (or the window's switch) turns this off.

Clone this wiki locally