Skip to content

Sega RingEdge / RingWide

Sega's Windows PC generation after the Lindbergh (2009): two variants, RingEdge (high-end) and RingWide (budget), on Windows Embedded. Tied to the ALL.Net network and locked by a keychip. Border Break, Hatsune Miku: Project DIVA Arcade, Sangokushi Taisen…

Identification

Field Value
Manufacturer Sega
Year 2009
Base x86 PCWindows Embedded 2009
Network ALL.Net (profiles, rankings, P-ras digital distribution)
Security keychip (gates boot/launch)
Output up to 2 screens 1920×1200, 5.1 sound

Architecture (PC)

Model CPU RAM GPU Storage
RingEdge (high-end) Intel Pentium Dual-Core E2160 (1.8 GHz) 1 GB DDR2 (PC-6400) NVIDIA GeForce 8800 GS (384 MB GDDR3, SM4.0) 32 GB SSD
RingWide (budget) Intel Celeron 440 (2.0 GHz) 1 GB DDR2 (PC-5300) ATI Radeon HD 2xxx (128 MB, SM4.0) SSD

Gigabit networking; both do 5.1 and dual screen. It's a Windows PC in an arcade case (after the Lindbergh's Linux, before Nu / ALLS).

Security, network & preservation (the real topic)

  • Keychip: a security chip gates the boot and launch of the game. Many resold boards lack their keychip (Sega property, returned at the end of the operator contract) → a major preservation obstacle.
  • ALL.Net: Sega's network (since 2004) for profiles/rankings/online play; extended as ALL.Net P-ras for digital distribution and updates. Server-dependent games → a separate preservation topic.
  • Preservation: the community has reverse-engineered the keychip protocols to keep cabinets running; imaging the SSD is the first step.

Notable games

Border Break (2009, AM2, first game), Hatsune Miku: Project DIVA Arcade, Sangokushi Taisen, Sega Network Taisen Mahjong MJ, Ollie King… (mostly networked / player-card games).

Faults & repair

Standard PC hardware:

Symptom Likely cause Lead
Won't boot/launch missing/dead keychip Critical part (Sega property); see preservation
Overheating / GPU crash GeForce 8800 / Radeon HD (fan/paste) Clean, re-paste, ventilate
SSD end of life wear Image the SSD
Reboots ATX PSU / capacitors Replace / recap
Controls / player card JVS I/O, card reader JVS / reader diagnosis

Modernisation & mods

The common ground for every JAMMA board

Video, power, control panel and upscalers depend on the cabinet rather than the board: everything is centralised in Modernising a cabinet. To run the board outside a cabinet (at home, on a display): supergun.

  • Hard disk ⚠️: a perishable medium — image the drive before it fails, then consider an SSD/CF replacement → PCB preservation hub.
  • Scan rate 📺: PC-based hardware — VGA output (31 kHz and above). ⚠️ A 15 kHz chassis is incompatible: you need a VGA/tri-sync monitor or a computer display. (Derived from the platform's PC nature documented above — not measured from MAME.)
  • FPGA / emulation: see the Emulation & FPGA section below.

Repair (technician)

  • Keychip: without the keychip (often missing from resold boards, Sega's property) the game won't start — check before suspecting the hardware.
  • x86 PC (Pentium Dual-Core + GeForce 8800 GS): PC diagnosis — PSU, RAM, GPU (caps/fan), SSD; a consumer GPU can have capacitor / BGA joint failures.
  • Network / player-card reader: an ALL.Net / JVS I/O dependency.

Methods: PCB fault-finding · Recap · Traces & vias

Emulation & FPGA

  • Emulation: Windows PC games → no MAME; preservation via SSD image + keychip (community RE protocols). No FPGA core.

Lineage

After the Lindbergh (Linux PC, 2005), before Nu / ALLS (2014+). The Europa-R variant (driving: Sega Rally 3, Initial D) is the same PC family.

Photos / assets

(To add: RingEdge vs RingWide board, keychip, SSD, JVS I/O.)

Sources & attribution

Review & corrections

How this space is used

Spotted a wrong value, an outdated procedure, a chip reference that does not match your board? Say so here, with what you observed (model, board revision, serial number, measurement). Every report is cross-checked against a source before anything changes — an unverifiable correction is published as “reported by …, not cross-checked” rather than silently applied.

Reading is open to everyone; posting requires signing in with Discord. Reports from the wiki's declared reviewers are handled first; anyone else's are read too, but go through a human before anything is changed.