Black Knight

Coverage

• PinMAME catalog

  BSD-3-Clause

  pinmame.catalog.97aa922bf8e4

  Pinned catalog driver records for the bk_l4 clone tree: bk_l4, bk_l3, bk_l2 and bk_f4

  97aa922bf8e4

  by

  PinMAME contributors

  rev

  97aa922bf8e4

• PinMAME source

  BSD-3-Clause

  pinmame.core.97aa922bf8e4

  Source locations

  src/wpc/sims/s7/full/bk.c: the four Black Knight drivers (CORE_GAMEDEF(bk,l4,...,s7_mS7S,0) and the CORE_CLONEDEF lines for bk_f4, bk_l3 and bk_l2), their S7_ROMSTART8088 ROM sets, and bkGameData = {GEN_S7, s7_dispS7, {0, ...}, &bkSimData, {{0}}, {0, {21, 22, 36, 0, 0, 0}}}: hw.flippers 0 (no FLIP_SWNO matrix switch, no FLIP_SOL), a zero inverted-switch mask, and special solenoids 17, 18 and 19 fired by switches 21, 22 and 36; its #define switch and solenoid names and the simulator tables are a keyboard simulator's guesses and are not used as evidence. src/wpc/s7games.c s7_dispS7 (DISP_SEG_7(1,0), DISP_SEG_7(1,1), DISP_SEG_7(0,0), DISP_SEG_7(0,1), DISP_SEG_BALLS(0,8), DISP_SEG_CREDIT(20,28)); src/wpc/core.h DISP_SEG_7/DISP_SEG_BALLS/DISP_SEG_CREDIT; src/wpc/s7.c and s7.h as in the System 7 controller profile; src/wpc/core.c core_updateSw and core_getSol; src/wpc/core.c layoutAlphanumericFrame (the extra 128x32 layout frame is a rendering aid, not a machine display)

  src/wpc/sims/s7/full/bk.csrc/wpc/s7games.csrc/wpc/core.hsrc/wpc/s7.csrc/wpc/core.clines for bk_f4, bk_l3 and bk_l2), their S7_ROMSTART8088 ROM sets, and bkGameData = {GEN_S7, s7_dispS7, {0, ...}, &bkSimData, {{0}}, {0, {21, 22, 36, 0, 0, 0

  by

  PinMAME contributors

  rev

  97aa922bf8e4

• Human review

  MIT

  controller-profile.pinmame-system-7

  Source locations

  Williams System 7 public address rules: sequential switch matrix 1-64, diagnostics -7 to -3, synthetic flipper buttons 81-88, DIP addressing bank * 8 + bit + 1, solenoids 1-24 with the game-on enable at 25, synthetic flipper outputs 45-48, lamps 1-64 and no GI channel

  internal:controllers/pinmame/system-7.json

  by

  pinmame-game-defs curation

  rev

  repository

• Operator manual

  manual.williams.black-knight.1980

  Source locations

  The English Black Knight game manual with paginated schematics, 70 pages, every schematic sheet marked 500, hosted by IPDB and retrieved live through an interactive browser; retained at external:pinmame-manuals/by-machine/williams.black-knight.1980/. PDF pages 6-19 are Instruction Booklet 16P-500-103 (December 1980): page 7 game operation, pages 8-10 bookkeeping and adjustments, pages 12-13 diagnostics, page 14 the lamp matrix, page 15 Figure 2 solenoid locations and chart, page 16 Table 4 solenoid connections, page 17 Figure 3 switch locations and chart, page 18 the switch matrix, page 19 auto-cycle and board self-tests. Page 26-28 CPU board logic, 32-34 driver board logic, 42 power wiring, 44 sound board assembly, 53-55 master display, 65 cabinet wiring, 66 playfield lamp wiring, 67 playfield solenoid wiring, 68 playfield switch wiring, 69 the separate lamp and switch matrix sheet.

  pages 6–19page 7pages 8–10pages 12–13
  PDF page 69, Switch Matrix, all 64 cells, compared cell by cell with the booklet's own matrix on PDF page 18checked

  PDF page 69, Lamp Matrix, all 64 cells, compared with the booklet's lamp matrix on PDF page 14checked

  PDF page 16, Table 4. Solenoid Connections and its noteschecked

  PDF page 15, the Solenoid Test and Figure 2. Playfield Solenoid Locations and Solenoid Chartchecked

  PDF pages 16-17, the Switch Test and Figure 3. Playfield Switch Locations and Switch Chart, with the drawing's registration against the retained tablechecked

  PDF pages 6-13 and 19: board requirements, game operation, speech, bookkeeping and adjustments, diagnostic procedures, auto-cycle and board self-testschecked

  PDF page 67, Playfield Solenoid Wiring Diagramchecked

  PDF page 68, Playfield Switch Wiring Diagramchecked

  PDF page 66, Playfield Lamp Wiring Diagramchecked

  PDF page 65, Cabinet Wiring Diagramchecked

  PDF pages 53-55, the master display foldout with the backbox lamps on 9P1checked

  PDF page 42, Power Wiring Diagram, with the K1 special relaychecked

  by

  Williams Electronics, Inc.; scan hosted by the Internet Pinball Database

  sha256

  3ce4bf0cf3e6…

• Operator manual

  manual.williams.black-knight.1980.schematic-diagrams

  Source locations

  21-page 300 dpi colour scan of the Black Knight schematic diagrams, with a previous owner's pen marks, hosted by IPDB. Used only as a cross-check of the wiring sheets in the manual (its pages 19-21 carry the cabinet, lamp, solenoid and switch wiring diagrams); where the two scans differ, the excerpts record it.

  page 300pages 19–21

  by

  Williams Electronics, Inc.; scan hosted by the Internet Pinball Database

  sha256

  7538cc080e02…

• Operator manual

  manual.williams.black-knight.1980.instruction-booklet

  Source locations

  A second, 400 dpi 1-bit scan of Instruction Booklet 16P-500-103 (15 pages), listed on IPDB as Instruction Booklet. Its tables agree with the copy in the manual; its page 12 (Figure 3) and page 10 (Figure 2) are the sharper renders used to register the location drawings onto the table frame.

  page 12page 10

  by

  Williams Electronics, Inc.; scan hosted by the Internet Pinball Database

  sha256

  4758a5fb5fe3…

• Service bulletin

  service-bulletin.williams.a-8762

  Williams A-8762 Retrofit Kit, BLACK KNIGHT Playfield, three pages: the kit replaces the locking mechanism and ball ramp switches with microswitches, and its wire colours identify the switches it replaces.

  ipdb.org
  Page 1: heading, GENERAL, KIT COMPLEMENT and the upper and lower playfield switch-identification stepschecked

  by

  Williams Electronics, Inc.; scan hosted by the Internet Pinball Database

  sha256

  6e7875c488be…

• Human review

  ipdb.310

  Source locations

  IPDB machine 310: Black Knight, Williams Electronics, November 1980, model number 500, Williams System 7, 13,075 units, design Steve Ritchie, art Tony Ramunni, software Larry DeMar; notable features 'Flippers (4), Pop bumper (1), Slingshots (2), 3-bank drop targets (4), Kick-out holes (2), Spinning target (1). Magna-Save on both inlanes. Split-level playfield with 3 ramps.'; the early stand-alone General Illumination relay and the later D-8345 power board; the vertical rebound switches cut into three of the four drop-target slots and Steve Ritchie's note on their removal. Retrieved live through an interactive browser (retained page SHA-256 above). Photographs https://www.ipdb.org/images/310/image-40.jpg (Stripped Playfield, 1200x2129, Brian Lee, SHA-256 27230f5f3e35cd656a27924d89e1edb25012de25c43552003588fdcc557eba5d) and https://www.ipdb.org/images/310/image-15.jpg (Under Playfield, 480x640, John Yates, SHA-256 047b26bf6153e84458e7987e656aa76429e0165b7be8555a92174c5c285d0b14), both acquired 2026-10-09, show the Magna-Save emblems and the two round magnets near the playfield sides; retained at external:pinmame-review-artifacts/black-knight-1980/ipdb-images/.

  ipdb.org

  by

  The Internet Pinball Database

  sha256

  d39d9b75a869…

• ROM analysis

  rom.black-knight.dip-port-reads

  Source locations

  Static reading of the bk_l4 program ROMs laid out as S7_ROMSTART8088 loads them: every extended-mode access to PIA 3 ($2800-$2803) and the one LDX #$2800. The only read of the DIP port's data is a discarded flag-clearing read; no code consumes the DIP banks. IC17, which holds that code, is the same chip in all four drivers.

  external:pinmame-roms/bk_l4.zip
  The PIA 3 access table, the $FC6A routine and its callerschecked

  by

  pinmame-game-defs curation

  sha256

  86e9da7a6170…

• VPX table

  vpx-table.black-knight-bord-3-0

  Source locations

  Community recreation by Bord, version 3.0, released November 2021 (built on new assets from Chris; VR by Uncle Paulie), from the operator's table archive. Exact playfield bounds left=0 top=0 right=952 bottom=1974; normalized coordinates are x/952 and y/1974. Geometry authority for named objects. The upper playfield's objects share the lower playfield's x/y frame.

  external:pinmame-vpx-sources/williams/black-knight-1980/source/Black Knight (Williams 1980).vpx

  by

  Bord

  rev

  3.0

  sha256

  bfaf38dfacd2…

• VPX script

  vpx-script.black-knight-bord-3-0

  Source locations

  Embedded script of the retained table, 124,592 bytes, byte-identical to the pinned corpus copy. Const cGameName="bk_l4" with S7.VBS and UseSolenoids=2. Runtime authority for: the SolCallback table (1 bsTrough.SolIn, 2-5 the drop-bank resets, 6 bsTrough.SolOut, 7 bsLock.SolOut, 8 bsSaucer.SolOut, 11 SolGi, 15 the bell sound, sLRFlipper/sLLFlipper driving both flippers on each side); cvpmMagnet MagnetR and MagnetL on solenoids 9 and 10; the trough cvpmBallStack (InitSw 20, 17, 18, 19), the lock (InitSw 0, 41, 42, 43) and the saucer on 24; the switch handlers 11-16, 21-27, 29-31, 33-39, 44, 45; the Magna-Save keys on switches 10 and 9; and InitLights, which binds each insert light to the lamp in its TimerInterval. Known defects not followed: SolCallback(23) = vpmNudge.SolGameOn (System 7 publishes game-on at 25); the apron light l7 carries TimerInterval 36 and lights with the jet bumper.

  external:pinmame-vpx-sources/williams/black-knight-1980/extracted-vpxtool/black-knight-bord-3.0/script.vbs

  by

  Bord

  sha256

  8f3b80424f73…

• VPX script

  vpx-script.vpinmame-s7-library

  Source locations

  The VPinMAME System 7 script library the retained table loads (script.vbs line 102: LoadVPM "01560000", "S7.VBS", 3.26), 144 lines, header 'Last Updated in VBS v3.61, copied from the operator's Visual Pinball Scripts folder. Byte-identical to scripts/s7.vbs in https://github.com/vpinball/vpinball at 6237ce52ef9cee9b9814881f6289d207bf9a3d2b. Its S7 Data constants name the game-on solenoid 25 and the flipper switches 82 (lower right) and 84 (lower left), which vpmKeyDown/vpmKeyUp set from the flipper keys.

  external:pinmame-vpx-sources/williams/black-knight-1980/vpinmame-scripts/s7.vbslines 102
  s7.vbs lines 20-38 and the flipper keys of vpmKeyDownchecked

  by

  VPinMAME / Visual Pinball script-library maintainers

  sha256

  88e6f2500f75…

• VPX table

  vpx-extraction.black-knight-bord-3-0

  Source locations

  Canonical manifest covering every sorted relative POSIX path, byte size and SHA-256 under extracted-vpxtool/black-knight-bord-3.0: 1323 files, 164805613 bytes, manifest SHA-256 dc16b9dbfc8b1d9fe199f26f8cd7daec7f16ce1d7938c1b8ae4f22e9a571948f, produced with vpxtool git:v0.33.3 from the retained table. Bounds left=0 top=0 right=952 bottom=1974.

  external:pinmame-vpx-sources/williams/black-knight-1980/extracted-vpxtool/black-knight-bord-3.0.manifest.json

  by

  vpxtool extraction

• VPX script

  vpx-script.black-knight-standalone-corpus

  Pinned corpus copy of the same table's original script (`Black Knight (Williams 1980).vbs.original`), byte-identical to the retained table's embedded script, which ties the retained table to the pinned known-working corpus.

  github.com

  by

  Bord; pinned copy in jsm174/vpx-standalone-scripts

  rev

  15d112648a1b

  sha256

  8f3b80424f73…

• Human review

  MIT

  human-review.black-knight-figure-3-registration

  Source locations

  Registration of the booklet's Figure 3 onto the retained table frame on the 400 dpi handbook render: eighteen control points whose convex hull contains every reading, a least-squares affine fit with 9.4 table-unit RMS residual and 17.3 maximum leave-one-out error, and the derived two-decimal coordinates for the outhole, the three ball-ramp positions, the three lockup-trough positions and the playfield tilt; the curator recomputes the fit from the recorded controls and readings. The registered outhole lies 7.6 table units from the outhole tab of the playfield cut-out that the retained table's playfield image shows under the apron. The fit script is retained at external:pinmame-review-artifacts/black-knight-1980/figure3-registration-fit.py.

  internal:evidence/excerpts/williams.black-knight.1980/switch-locations.md

  by

  pinmame-game-defs curation

  rev

  repository

• Runtime run

  runtime.black-knight.solenoid-test

  Source locations

  LibPinMAME harness run of bk_l4 with tools/run_pinmame_harness.py, library pinmame64.dll built from the pinned PinMAME revision (SHA-256 dfcd9f9407dcb4e107d6ea066ceaccdb07333b552cd30fc1bfc491a385a4dead), ROM archive bk_l4.zip from the operator's authorized ROM corpus (SHA-256 86e9da7a6170c9d45fb0b37a3f571452d1e79b1e94cc62cdddedf7cd032f6e63, CRCs matching the pinned driver), in an isolated state directory, with direct public switch writes only (PinMAME keyboard handling and the driver's built-in simulator off). Scenario tools/harness-scenarios/system-7/black-knight-solenoid-test.json (SHA-256 f542658cf0c1aa105daba00c06c1e0f1f5d19de0f1ef1cb7d06ba6edb1ca7825). A first power-up from empty CMOS stops on the game-identification screen, so the state directory was initialized by exactly one prior empty-NVRAM boot (scenario black-knight-nvram-init-boot.json, SHA-256 0f76a557b40f4a90ea9c8b4bc397316db1e4b34a28576859d527eeaaa780b913; raw run SHA-256 2df7abdd46907054676a120571b768e863cae93ef5e6f986a3af9183980418ce). Diagnostics: Manual-Down plus Advance enters the display digits test; Auto-Up and Advance step Test 00 (sound), Test 01 (lamp test: all 64 lamp addresses flash) and Test 02, each shown in the credit displays (indexes 6 and 7). In Test 02 with Manual-Down each Advance moves one step: the ball-in-play displays (indexes 4 and 5) show 01 to 24 while the ROM pulses public solenoid 1 to 24 respectively, and step 25 toggles the game-on enable at 25. Public 25 asserts on entering diagnostics; 16 is energized from power-up. The whole run directory is pinned by external:pinmame-runtime-evidence/black-knight-1980.manifest.json (35 files, 6702842 bytes, manifest SHA-256 8dcfd956cb4f81c9b881aa60f7e92820d0cb35ef137dc8f63c3ca322114e4538). No ROM bytes or NVRAM blobs are retained in this repository.

  external:pinmame-runtime-evidence/black-knight-1980/run-sol.json

  by

  pinmame-game-defs curation

  rev

  97aa922bf8e4

  sha256

  bb2a1c7c49d3…

• Runtime run

  runtime.black-knight.switch-test

  Source locations

  LibPinMAME harness run of bk_l4 with tools/run_pinmame_harness.py, library pinmame64.dll built from the pinned PinMAME revision (SHA-256 dfcd9f9407dcb4e107d6ea066ceaccdb07333b552cd30fc1bfc491a385a4dead), ROM archive bk_l4.zip from the operator's authorized ROM corpus (SHA-256 86e9da7a6170c9d45fb0b37a3f571452d1e79b1e94cc62cdddedf7cd032f6e63, CRCs matching the pinned driver), in an isolated state directory, with direct public switch writes only (PinMAME keyboard handling and the driver's built-in simulator off). Scenario tools/harness-scenarios/system-7/black-knight-switch-test.json (SHA-256 ea4b8cc2b752cfa68973fb9984e305d9becedf5163724060848d64dce4e6b2d8). A first power-up from empty CMOS stops on the game-identification screen, so the state directory was initialized by exactly one prior empty-NVRAM boot (scenario black-knight-nvram-init-boot.json, SHA-256 0f76a557b40f4a90ea9c8b4bc397316db1e4b34a28576859d527eeaaa780b913; raw run SHA-256 7952617a8ee2ad4f71e8641b3244486741e44f569b8358d30480649e958ca394). Test 03 (switch test): nothing is reported at rest; closing each public switch 1 to 46 alone makes the ball-in-play displays show that number, so every matrix switch reads 1 when closed and 0 open with no inversion, including 28, 32 and 40, which no production switch occupies; closing 47 to 64 is never reported. Closing 21, 22 and 36 also publishes 17, 18 and 19. The whole run directory is pinned by external:pinmame-runtime-evidence/black-knight-1980.manifest.json (35 files, 6702842 bytes, manifest SHA-256 8dcfd956cb4f81c9b881aa60f7e92820d0cb35ef137dc8f63c3ca322114e4538). No ROM bytes or NVRAM blobs are retained in this repository.

  external:pinmame-runtime-evidence/black-knight-1980/run-sw.json

  by

  pinmame-game-defs curation

  rev

  97aa922bf8e4

  sha256

  141ee097c5e0…

• Runtime run

  runtime.black-knight.gameplay-causality

  Source locations

  LibPinMAME harness run of bk_l4 with tools/run_pinmame_harness.py, library pinmame64.dll built from the pinned PinMAME revision (SHA-256 dfcd9f9407dcb4e107d6ea066ceaccdb07333b552cd30fc1bfc491a385a4dead), ROM archive bk_l4.zip from the operator's authorized ROM corpus (SHA-256 86e9da7a6170c9d45fb0b37a3f571452d1e79b1e94cc62cdddedf7cd032f6e63, CRCs matching the pinned driver), in an isolated state directory, with direct public switch writes only (PinMAME keyboard handling and the driver's built-in simulator off). Scenario tools/harness-scenarios/system-7/black-knight-gameplay-causality.json (SHA-256 4f1de42950c7fc0610a88b7eb90640d0fd7a94e9487379ce6e630bd0c35ccc82). A first power-up from empty CMOS stops on the game-identification screen, so the state directory was initialized by exactly one prior empty-NVRAM boot (scenario black-knight-nvram-init-boot.json, SHA-256 0f76a557b40f4a90ea9c8b4bc397316db1e4b34a28576859d527eeaaa780b913; raw run SHA-256 f607ff7b5e19b79743ceced5e4faa6bd197d746821b282e59bd2e51ab21b58f2). With balls on 17, 18 and 19: a coin on 4 posts credits; the credit button (3) asserts 25, pulses 2-5 and throws with 6; 21, 22 and 36 publish 17, 18 and 19; the synthetic buttons 82 and 84 publish 45/46 and 47/48; each bank completed with its three switches held closed fires its reset (25-27 -> 2, 29-31 -> 3, 33-35 -> 4, 37-39 -> 5) and lights an arrow (25, 29, 33, 37) and a Magna-Save lamp (9, then 10); the left and right Magna-Save buttons (10, 9) then energize 10 and 9; closing 24 pulses 8; a ball on 41 is held and 6 throws a new one; a ball on 20 draws repeated pulses of 1; three playfield-tilt closures (46) pulse 11 twice and then hold 11, drop 25 and light the tilt lamp 3. The whole run directory is pinned by external:pinmame-runtime-evidence/black-knight-1980.manifest.json (35 files, 6702842 bytes, manifest SHA-256 8dcfd956cb4f81c9b881aa60f7e92820d0cb35ef137dc8f63c3ca322114e4538). No ROM bytes or NVRAM blobs are retained in this repository.

  external:pinmame-runtime-evidence/black-knight-1980/run-play.json

  by

  pinmame-game-defs curation

  rev

  97aa922bf8e4

  sha256

  ce4901c73373…

• Runtime run

  runtime.black-knight.multiball

  Source locations

  LibPinMAME harness run of bk_l4 with tools/run_pinmame_harness.py, library pinmame64.dll built from the pinned PinMAME revision (SHA-256 dfcd9f9407dcb4e107d6ea066ceaccdb07333b552cd30fc1bfc491a385a4dead), ROM archive bk_l4.zip from the operator's authorized ROM corpus (SHA-256 86e9da7a6170c9d45fb0b37a3f571452d1e79b1e94cc62cdddedf7cd032f6e63, CRCs matching the pinned driver), in an isolated state directory, with direct public switch writes only (PinMAME keyboard handling and the driver's built-in simulator off). Scenario tools/harness-scenarios/system-7/black-knight-multiball.json (SHA-256 9cc83f4b4fbf924d41bc46853d308b03918a1f90abf67c7a28492a408ae95349). A first power-up from empty CMOS stops on the game-identification screen, so the state directory was initialized by exactly one prior empty-NVRAM boot (scenario black-knight-nvram-init-boot.json, SHA-256 0f76a557b40f4a90ea9c8b4bc397316db1e4b34a28576859d527eeaaa780b913; raw run SHA-256 be1a27c2e41870b6df9bd9a39e505f1cf0f0eaf21679f08579371516d63573c4). After a game start, each ball locked on 41 and 42 is held and 6 throws a new ball; with the third ball on 43 the ROM pulses 2-5, energizes 11 and pulses the Multi-Ball release 7 while all three lockup switches are still closed, and pulses 7 and 11 again after the switches open. The whole run directory is pinned by external:pinmame-runtime-evidence/black-knight-1980.manifest.json (35 files, 6702842 bytes, manifest SHA-256 8dcfd956cb4f81c9b881aa60f7e92820d0cb35ef137dc8f63c3ca322114e4538). No ROM bytes or NVRAM blobs are retained in this repository.

  external:pinmame-runtime-evidence/black-knight-1980/run-mb.json

  by

  pinmame-game-defs curation

  rev

  97aa922bf8e4

  sha256

  4a67e405861d…

• Runtime run

  runtime.black-knight.four-player-displays

  Source locations

  LibPinMAME harness run of bk_l4 with tools/run_pinmame_harness.py, library pinmame64.dll built from the pinned PinMAME revision (SHA-256 dfcd9f9407dcb4e107d6ea066ceaccdb07333b552cd30fc1bfc491a385a4dead), ROM archive bk_l4.zip from the operator's authorized ROM corpus (SHA-256 86e9da7a6170c9d45fb0b37a3f571452d1e79b1e94cc62cdddedf7cd032f6e63, CRCs matching the pinned driver), in an isolated state directory, with direct public switch writes only (PinMAME keyboard handling and the driver's built-in simulator off). Scenario tools/harness-scenarios/system-7/black-knight-four-player-displays.json (SHA-256 519da4dbc93e9a090e73ba33929d16ec76e244997db85c4b2c00a9f699d87458). A first power-up from empty CMOS stops on the game-identification screen, so the state directory was initialized by exactly one prior empty-NVRAM boot (scenario black-knight-nvram-init-boot.json, SHA-256 0f76a557b40f4a90ea9c8b4bc397316db1e4b34a28576859d527eeaaa780b913; raw run SHA-256 4de14bfaa319c323a231be1ffdae1340833cec69fa07e24750de5edb90cfadd6). Two coins and four presses of the credit button start a four-player game; each player's 10 points from switch 21 appears on PinMAME display index 2 (player 1), 3 (player 2), 0 (player 3) and 1 (player 4), the ball in play on indexes 4 and 5 and the credits on indexes 6 and 7. The whole run directory is pinned by external:pinmame-runtime-evidence/black-knight-1980.manifest.json (35 files, 6702842 bytes, manifest SHA-256 8dcfd956cb4f81c9b881aa60f7e92820d0cb35ef137dc8f63c3ca322114e4538). No ROM bytes or NVRAM blobs are retained in this repository.

  external:pinmame-runtime-evidence/black-knight-1980/run-4p.json

  by

  pinmame-game-defs curation

  rev

  97aa922bf8e4

  sha256

  72a305dd6a57…

• Runtime run

  runtime.black-knight.l3-solenoid-test

  Source locations

  LibPinMAME harness run of bk_l3 with tools/run_pinmame_harness.py, library pinmame64.dll built from the pinned PinMAME revision (SHA-256 dfcd9f9407dcb4e107d6ea066ceaccdb07333b552cd30fc1bfc491a385a4dead), ROM archive bk_l3.zip from the operator's authorized ROM corpus (SHA-256 f030e18a7c37bf56fbc22b234593b55954fe56c05535a933b70819fd736aad2b, CRCs matching the pinned driver), in an isolated state directory, with direct public switch writes only (PinMAME keyboard handling and the driver's built-in simulator off). Scenario tools/harness-scenarios/system-7/black-knight-l3-solenoid-test.json (SHA-256 5c2145a423c67576e9242ef47766da34610145914d835f177b7f43e285018d0f). A first power-up from empty CMOS stops on the game-identification screen, so the state directory was initialized by exactly one prior empty-NVRAM boot (scenario black-knight-l3-nvram-init-boot.json, SHA-256 918963bec06cf99a01b0befc5d0875ebbee55039e3c9ad090b28ec196e7e9b9e; raw run SHA-256 6a5e6fad248efdc5c1f46584af78583bc855dfa0f4123f1a55d299b802585a49). The solenoid-test scenario on the L-3 ROM: the same displayed step numbers 01 to 24 pulse public 1 to 24 and step 25 toggles 25. The whole run directory is pinned by external:pinmame-runtime-evidence/black-knight-1980.manifest.json (35 files, 6702842 bytes, manifest SHA-256 8dcfd956cb4f81c9b881aa60f7e92820d0cb35ef137dc8f63c3ca322114e4538). No ROM bytes or NVRAM blobs are retained in this repository.

  external:pinmame-runtime-evidence/black-knight-1980/run-sol-l3.json

  by

  pinmame-game-defs curation

  rev

  97aa922bf8e4

  sha256

  dfe1b2f87c69…

• Runtime run

  runtime.black-knight.f4-solenoid-test

  Source locations

  LibPinMAME harness run of bk_f4 with tools/run_pinmame_harness.py, library pinmame64.dll built from the pinned PinMAME revision (SHA-256 dfcd9f9407dcb4e107d6ea066ceaccdb07333b552cd30fc1bfc491a385a4dead), ROM archive bk_f4.zip from the operator's authorized ROM corpus (SHA-256 42e37f2e61ce97c0be0965636d59f6b0b918784ff150159c41261fa179b1c666, CRCs matching the pinned driver), in an isolated state directory, with direct public switch writes only (PinMAME keyboard handling and the driver's built-in simulator off). Scenario tools/harness-scenarios/system-7/black-knight-f4-solenoid-test.json (SHA-256 d62e0b2d0da7d4d866e20ca42e248be90ed7831ad5dfdfe94359c5531bec23fd). A first power-up from empty CMOS stops on the game-identification screen, so the state directory was initialized by exactly one prior empty-NVRAM boot (scenario black-knight-f4-nvram-init-boot.json, SHA-256 cadcef42b1ac35a7899ed93617914df17fa7ea458d60b52b457e40f255cf3bc2; raw run SHA-256 46cee6a306fdd1f7865c7d504220e7f697c677ae0c1e041611337ef05e448caf). The solenoid-test scenario on the French-speech L-4 ROM: the same displayed step numbers 01 to 24 pulse public 1 to 24 and step 25 toggles 25. The whole run directory is pinned by external:pinmame-runtime-evidence/black-knight-1980.manifest.json (35 files, 6702842 bytes, manifest SHA-256 8dcfd956cb4f81c9b881aa60f7e92820d0cb35ef137dc8f63c3ca322114e4538). No ROM bytes or NVRAM blobs are retained in this repository.

  external:pinmame-runtime-evidence/black-knight-1980/run-sol-f4.json

  by

  pinmame-game-defs curation

  rev

  97aa922bf8e4

  sha256

  683ca047cc9d…