Wheel of Fortune

Partial
Completion19%

Stern2007SAMstern.wheel-of-fortune.2007 Updated 2026-08-30

Wire it up

what an authoring tool needs first
Bind this ROM
wof_500

21 ROM sets resolve to this machine. Clones share the definition unless a hardware difference is listed.

Controller platform
pinmame.sam

PinMAME already reports logical active state. Do not invert again in the table — normally-closed is a physical fact recorded per switch, not a runtime transform.

Displays

No display inventory recorded yet.

Address space
Solenoids
33–33 (1)

Coverage

Partial

Real evidence exists, but authoring requirements are still missing or in conflict. Verify before shipping a table.

Completion19%

Progress is derived from the fixed author-readiness requirements. It helps rank unfinished work, but only a 100% author-ready definition passes the publication gate.

Catalog Identity
validated
Address Enumeration
unknown
Semantic Naming
unknown
Physical Wiring
unknown
Mechanisms
unknown
Variant Coverage
candidate
Recreation Knowledge
unknown
Still missing · 13
Driver MappingInput EnumerationInput SemanticsOutput EnumerationOutput SemanticsDisplay InventoryMechanism InventoryMechanism BehaviorPolarityVariant DifferencesRecreation NotesProvenanceSpatial Placement

Controlled devices

Everything the ROM can energise, grouped the way a table author builds it.

Virtual & other outputs

1
1 shown
# Name Device ID Evidence
33
PinMAME SAM game-on state
solenoid.33 candidate

Recreation notes

Working knowledge that has no schema field yet — edition differences, tuning values, pitfalls.

Coverage: partial - machine identity plus candidate-only I/O attachments. Playfield devices, wiring, mechanisms, and behavior are evidenced only as unverified candidates.

This record was promoted from the generated catalog stub stub.pinmame.wof_500 by the catalog-wide identity pass of 2026-08-29. The promotion resolves machine identity and carries the catalog's residual driver grouping over unchanged, the platform and device attachments below were added by the 2026-08-29/30 candidate passes and assert nothing beyond candidate provenance. Every requirement in the definition's coverage.missing is genuinely outstanding.

Identity

  • PinMAME catalog: root driver wof_500, description "Wheel of Fortune (V5.0)", manufacturer "Stern", catalog year "2007".
  • OPDB record G417d-MJkXV (IPDB 5254) names this machine "Wheel of Fortune" (Stern, manufacture date 2007-10-01); the resolved identity rests on the agreement of the PinMAME catalog and this reviewed mapping.
  • The definition's driver list is exactly the clone tree PinMAME declares under wof_500; whether every listed driver really runs on this physical machine is unverified.

Drivers this record holds

  • wof_100 (2007, Stern, clone of wof_500).
  • wof_200 (2007, Stern, clone of wof_500).
  • wof_200f (2007, Stern, clone of wof_500).
  • wof_200g (2007, Stern, clone of wof_500).
  • wof_200i (2007, Stern, clone of wof_500).
  • wof_300 (2007, Stern, clone of wof_500).
  • wof_300f (2007, Stern, clone of wof_500).
  • wof_300g (2007, Stern, clone of wof_500).
  • wof_300i (2007, Stern, clone of wof_500).
  • wof_300l (2007, Stern, clone of wof_500).
  • wof_400 (2007, Stern, clone of wof_500).
  • wof_400f (2007, Stern, clone of wof_500).
  • wof_400g (2007, Stern, clone of wof_500).
  • wof_400i (2007, Stern, clone of wof_500).
  • wof_401l (2007, Stern, clone of wof_500).
  • wof_500 (2007, Stern).
  • wof_500f (2007, Stern, clone of wof_500).
  • wof_500g (2007, Stern, clone of wof_500).
  • wof_500i (2007, Stern, clone of wof_500).
  • wof_500l (2007, Stern, clone of wof_500).
  • wof_602h (2009, Stern, clone of wof_500).

PinMAME source contract (candidate)

  • The pinned PinMAME source declares wof_500 at src/wpc/sam.c:2878 with machine module sam1; the definition declares controller platform pinmame.sam from it.

What a curator must establish next

Full input, output, and display enumeration with semantic names; physical wiring and polarity; mechanism inventory and behavior; variant differences across the clone tree; recreation knowledge from a manual, schematic, or known-working table; runtime provenance; and a normalized spatial placement for every physical device. No manual, schematic, or runtime-harness evidence is retained for this machine yet; the candidate sections above are the only retained I/O evidence so far.

ROM sets

Every driver that resolves to this physical machine.

ROM set Description Year Parent Hardware
wof_602hWheel of Fortune (V6.02 Home Rom) 2009wof_500—
wof_500lWheel of Fortune (V5.0 Spanish) 2007wof_500—
wof_500iWheel of Fortune (V5.0 Italian) 2007wof_500—
wof_500gWheel of Fortune (V5.0 German) 2007wof_500—
wof_500fWheel of Fortune (V5.0 French) 2007wof_500—
wof_500Wheel of Fortune (V5.0) 2007——
wof_401lWheel of Fortune (V4.01 Spanish) 2007wof_500—
wof_400iWheel of Fortune (V4.0 Italian) 2007wof_500—

Parent set: wof_500 — clones share this definition unless a hardware difference is noted.

Evidence

Every claim above traces to one of these. When they disagree: a known-working VPX script wins on controller addresses and causality, the manual wins on wiring and construction, pinned PinMAME wins on emulator routing and display layout.

  • PinMAME catalog

    BSD-3-Clause

    pinmame.catalog.8371478a7640

    PinmameGetGames

    by
    PinMAME contributors
    rev
    8371478a7640
  • PinMAME source

    BSD-3-Clause

    pinmame.core.8371478a7640

    src/wpc/sam.c:2878 (machine module sam1)

    by
    PinMAME contributors
    rev
    8371478a7640

Something wrong or missing?

This definition still has 13 unmet requirements, listed under Missing data below. Fixes belong in the definition itself — editing on GitHub forks it for you and opens the pull request.

Cite a source for anything you change — a manual page, a line in a working VPX script, PinMAME source, or a reading from the machine's own service menu. Claims without provenance cannot be validated.

Same platform

Missing data

What this game definition still needs to reach 100% and become author-ready.

  • ROM compatibility

    Verify which PinMAME drivers and firmware variants belong to this physical machine.

  • Complete input inventory

    Account for every switch, service input and diagnostic address, including unused positions.

  • Input functions

    Validate which physical sensor or cabinet control each input represents and when it activates.

  • Complete output inventory

    Account for every coil, motor, lamp, flasher and general-illumination circuit, including unused addresses.

  • Output functions

    Validate the physical device, function and fitted quantity behind each output binding.

  • Displays

    Verify every display, its layout and its controller bindings.

  • Mechanism inventory

    Document every mechanism, its moving parts, actuators, sensors and connections.

  • Mechanism behavior

    Validate mechanism operation, ball paths, home positions, startup and reset behavior.

  • Switch construction and polarity

    Verify normally open or closed contacts and how PinMAME delivers their active states.

  • Edition and firmware differences

    Document supported hardware and firmware differences without combining incompatible editions.

  • Recreation knowledge

    Complete the source-backed behavior and assembly notes needed to recreate the machine.

  • Evidence and sources

    Back the remaining claims with attributable sources, exact locators, retained excerpts and verified hashes.

  • Physical device locations

    Establish validated playfield locations for every physical sensor, actuator and light emitter, including bulb counts and justified projections.