| ParlorNet Turn-based game server for any computer, old or new | |
| Clients | Protocols | Browsers | Telnet programs | Docs | Source |
Status: research notes, 2026-11-21. Every fact carries a source tag like [S1] (list in section a). Anything not backed by a source is marked UNVERIFIED. Code locations are offsets into the program's TEXT segment (TEXT:0x5848).
Method: static analysis only. The ST disk image was read with a small FAT12 reader in Python. The GEMDOS program header and relocation table were parsed, and the 68000 code was disassembled with capstone 5. The program is compiled BASIC: its runtime raises errors as [1][Error +111][Return] alerts, the GFA-BASIC 3 style (compiler identity UNVERIFIED). User code calls the runtime through a4 (a4 = 0x13B80 after start-up) and keeps variables at negative offsets from a5. The runtime entry points for OUT, INP and INP? were identified by following them to their BIOS trap #13 calls. Nothing was run and no modem or serial port was used.
| Item | Value | Source |
|---|---|---|
| Port | ST serial port, BIOS device 1 (AUX). Output Bconout(1, b), input Bconin(1), polled with Bconstat(1) (runtime TEXT:0xF05C, 0xF876, 0xF864) | [S1] |
| Serial setup | XBIOS 15 Rsconf(speed, 1, -1, -1, -1, -1) at start-up (TEXT:0x110), after the baud dialog (0x98D2) and on entering the terminal screen (0x68EE). Flow control 1 = XON/XOFF. UCR, RSR, TSR and SCR are left unchanged | [S1] |
| Default speed | Rsconf code 7 = 1200 baud (TEXT:0x10A). The manual recommends 1200 | [S1][S2] |
| Baud dialog | "Choose baud rate. 300 / 1200 / 2400". As compiled: button 1 sets code 9 (300), then a second test of button 1 overwrites it with code 4 (2400). Button 2 sets code 7 (1200). Button 3 changes nothing (TEXT:0x9890-0x98BA). So "300" gives 2400 and "2400" keeps the previous speed. Whether this is a source bug or a deliberate remap is UNVERIFIED | [S1] |
| Dial | Pulse/tone dialog, then ATDP<number> or ATDT<number> followed by CR. Every character is masked with 0x7F and sent with OUT 1 (TEXT:0x664C, 0x687E, 0x689C) | [S1] |
| Auto answer | menu item sends ATS0=1 CR then ATZ CR, in that order (TEXT:0x991C-0x9940). On most Hayes modems ATZ reloads the stored profile and may clear S0=1. The manual also suggests typing ATA in the terminal screen when the phone rings | [S1][S2] |
| Terminal screen | full-screen dumb terminal: received bytes masked to 7 bits and printed (CR also prints LF). Typed keys are sent raw. CR is sent as CR LF, local echo optional ("Full=no echo / Half=echo"). Leaves on a mouse click (TEXT:0x68BE) | [S1][S2] |
| Connect detection | none. The game screen's receive loop (TEXT:0x533A) polls Bconstat(1) and dispatches every byte, whatever its origin | [S1] |
| Display | monochrome high resolution only ("requires a mono monitor") | [S1][S2] |
Two arrays of 27 entries (indices 0..26): count A[i] (checkers on point i) and colour B[i] (1 = light, 2 = dark, 0 = none) [S1] (TEXT:0x6102-0x62F6).
Receive dispatch is SELECT on each byte (TEXT:0x5848) [S1]:
| Bytes | Name | Sender / when | Receiver action |
|---|---|---|---|
| 20-7E | chat character | typed chat line, sent whole when the player presses RETURN, each character AND 0x7F (TEXT:0x650E -> 0x664C) | appended to the incoming chat line (up to 79 characters shown) |
| 0D | end of chat line | after a chat line | shows the line in the message area |
| other bytes below BF, and LF | - | - | ignored |
| D3 | new-game request from dark | dark player picks "Begin a new game" (TEXT:0x971E) | acted on only by the light side: records the peer's request. If the local request is also set, the game starts, otherwise the screen shows the opponent's request |
| D4 | new-game request from light | light player picks "Begin a new game" (TEXT:0x977E) | acted on only by the dark side, as above |
| xx yy (no opcode) | opening dice | the dark side, right after both requests are exchanged: rolls one die each (dark, light), re-rolls ties, sends the two raw bytes (1..6) (TEXT:0x7662-0x7686) | the light side waits for exactly two bytes (TEXT:0x7780). Higher die moves first. The top die is dark's, the bottom light's [S2] |
| BF d1 d2 | dice roll | the side whose turn begins, after it rolls (INT(RND*6)+1 twice, TEXT:0x6E16, 0x6E58). Values 1..6 | if not our turn: store and show the opponent's dice (TEXT:0x5406) |
| E5 f t | one checker step | after each local step on our turn, if not in manual (computer) mode. f and t are 200 + index in the receiver's numbering (1..24 shifted by 12; 25 and 26 unchanged), so 0xC9-0xE2 (TEXT:0x65EE, 0x6CE6) | if not our turn: subtract 200 and perform the step as if clicked, including hits (TEXT:0x6D1C) |
| E4 | pass (end of turn) | PASS button on our turn (TEXT:0x52FA). The sender's turn ends | if not our turn: our turn begins, and **we roll at once and send BF d1 d2** (TEXT:0x54DA) |
| F0 | cube turned | click on the cube square on our turn (TEXT:0x52A0); also when the opening winner chooses "Roll" with the opening-roll option (then followed by BF) | if not our turn: double the displayed cube and flash it (TEXT:0x54F6) |
| F2 | position verification request | Options / Position verification, after "Compare positions on both players boards?" (TEXT:0x6A30) | replies at once with F1 + 52 bytes (below), whatever the turn |
| F1 (A1 B1 ... A24 B24) A25 B25 A26 B26 | position dump | reply to F2: counts and colours in the sender's numbering, unshifted (TEXT:0x550C) | read only by the requester, which busy-waits for it. It stores sender 1..12 as its 13..24 and 13..24 as 1..12, compares, and reports "boards are correct" or "do NOT match" (TEXT:0x6A3A). If the first byte is not F1, the check is silently abandoned |
| FE (A1 B1 ... A24 B24) A25 B25 A26 B26 turn cube | transmit positions | Options / Transmit positions (TEXT:0x841C). turn = sender's turn flag (0/1), cube = displayed cube value as one byte | overwrites the board with the same 12-point rotation; our turn = 1 if turn was 0, else 0; cube set to cube; full redraw (TEXT:0x559C) |
Notes [S1]:
Dark ST (D) and light ST (L), both connected; hex bytes.
D->L 48 69 20 42 6F 62 0D "Hi Bob" CR (chat)
D->L D3 dark requests a new game
L->D D4 light requests; both sides now start
D->L 05 03 opening dice: dark 5, light 3 -> dark moves first,
playing the 5-3 (opening-roll option off)
D->L E5 CD D2 step 8->3 in dark's own numbering = dark index
17->22 = light index 5->10, sent as 200+5, 200+10
D->L E5 CF D2 step 6->3 (dark index 19->22 = light 7->10)
D->L E4 pass
L->D BF 06 02 light rolls 6-2 automatically and sends it
L->D E5 ... light's steps
L->D E4
D->L BF 04 04 dark rolls
...
D->L F2 dark asks to verify
L->D F1 + 52 bytes light's board
Possible, as a "virtual peer", but a poor fit for a server-authoritative table. What a ParlorNet bridge would have to do:
Effort: small code (ten opcodes), but it needs a serial or modem bridge plus two backgammon/1 extensions: client-supplied dice for one seat, and a cube take/drop path. Confidence: high for the opcodes, operand layouts and coordinate rotation, which were read from the code. Medium for the opening-roll behaviour and the auto-answer sequence. Value: low. It is a 1991 freeware program for monochrome STs, and modem-to-modem play is its only network mode.
| These pages cover every ParlorNet server. | Source code | ParlorNet is free software. |