SCRYReference

Reference

Every tool of both servers has a page, with an example you can try.

MAME

67 tools in 17 families. The rules the MAME tools share.

  • SessionStarting a MAME session, asking what state it is in, finding its window, choosing a cpu and ending it.
  • MachineWhat the emulated machine is made of, how the debugger holds each cpu, and what MAME writes to its logs.
  • NamesSymbol names for addresses: look up a name or an address in the symbol table of your program.
  • RunThe tools that let the program run and stop it again.
  • BreakpointsBreakpoints and watches the server saves by name and sets again in later sessions.
  • ReadReading what the stopped program holds: memory, registers, code, and which of its screens is showing.
  • ScreenSeeing a board's graphics as data: the palette entry behind each pixel, tiles decoded from ROM or memory, and the draws a board makes.
  • TimelineMAME's tools that load a project's graphics manifest and show, frame by frame, when a write happened and which code set a colour.
  • ScanFinding the address of a value nobody has named yet.
  • WriteChanging the machine: memory, a register, a reset, and any line the debugger console takes.
  • CommentsNotes on addresses of the program, saved with the breakpoints and shown in the disassembly.
  • LuaPressing the board's inputs, running Lua inside MAME, and choosing whether the machine runs at real speed.
  • StatesSaved states: the whole emulated machine written to a file, listed, and loaded back.
  • CapturesSaving the screen and the sound to files: a still, a series of frames, a video, a recording, and the list of them.
  • FilesComparing pictures and recordings on disk, in numbers, with no machine running.
  • SequencesRunning several calls as one: a list of steps, an input with its check, and a session written as a replay script.
  • ProjectSaving what a session learned into the repository's .scry/ folder, after a review.

DOSBox-X

62 tools in 17 families. The rules the DOSBox-X tools share.

  • SessionChecking the DOSBox-X build, starting a session, asking what state it is in, finding its window and ending it.
  • MachineWhat the DOS machine holds at a stop (memory blocks, drivers, interrupt vectors) and what the program and the emulator write to the log.
  • ReadReading what the stopped program holds: memory, registers, code, and which of its screens is showing.
  • ScreenReading what the screen shows at a stop: its text or its picture, its colours, and a short hash of it.
  • ScanFinding the address of a value nobody has named yet.
  • WriteChanging the machine: memory, a register, and any command the debugger takes.
  • HardwareThe hardware behind the cpu: I/O ports, the interrupt controllers and the A20 line.
  • RunThe tools that let the program run and stop it again.
  • BreakpointsBreakpoints and watches the server saves by name and sets again in later sessions.
  • StatesSaved states: the whole emulated machine written to a file, listed, and loaded back.
  • NamesSymbol names for addresses: load your program's symbol table, then look up a name or an address in it.
  • CommentsNotes on addresses of the program, saved with the breakpoints and shown in the disassembly.
  • InputSending keys, mouse buttons and pointer moves to the DOS program, and checking that it reacted.
  • CapturesSaving the screen and the sound to files: a still, a series of frames, a video, a recording, and the list of them.
  • FilesComparing pictures and recordings on disk, in numbers, and checking a file the DOS program wrote.
  • SequencesRunning several calls as one: a list of steps, an input with its check, and a session written as a replay script.
  • ProjectSaving what a session learned into the repository's .scry/ folder, after a review.