ATARI MUTINEER
[H] HOMEATARI MUTINEER / DOCUMENTATION / 1.3.183

Troubleshooting

Diagnose boot, listener, terminal, caller, door, and storage problems.

Browse documentation

Troubleshooting

Troubleshoot the active REMMS path. Do not switch a live board back to an old MMS communication layer to work around a failure.

Altirra Does Not Boot The Board

  • Confirm the Mutineer ATR is mounted as D1:.
  • Confirm SpartaDOS X is mounted as the cartridge.
  • Confirm BASIC is enabled.
  • Confirm fast boot is enabled.
  • If you only want to inspect the ATR, boot a utility disk as D1: and mount Mutineer as a secondary disk so it does not auto-start.

Expected startup:

AUTOEXEC.BAT -> RHND850.COM -> REMMS.COM -> BASIC -> WFC

No Listener Or No Connection

  • Confirm the Atari 850 device is enabled.
  • Confirm 850 emulation is Full.
  • Confirm the modem is a child device of the 850.
  • Confirm the modem is inbound/listen on 127.0.0.1:6507.
  • Confirm no other Altirra instance owns port 6507.
  • Keep Telnet LF translation off.
  • Leave CIO R: patch off.

The caller should see:

CONNECTED PRESS [RETURN]

If the caller sees WFC dashboard text before that prompt, the BBS is leaking local dashboard output to the modem and should not be used as a release image.

Return Does Not Work

Use a normal CR or CR/LF Return from the terminal client. In PuTTY, use Telnet, set local echo to Auto or Force off, and leave local line editing off.

If the A command says HIT <RETURN> and then ignores Return, the runtime is using an older CORE/REMMS combination. Use a current release ATR.

First User Is Not Sysop

The first completed registration becomes user number 1 and access level 9. If a test user was created first, restore your clean ATR backup or use offline maintenance to repair the user/access files.

Files involved:

  • D1:>DATA>USERS.DAT
  • D1:>DATA>USERS.IDX
  • D1:>DATA>NEXTUSER.DAT
  • D1:>DATA>ACL.CFG

Cannot Reach A Module

  • Confirm the main menu prompt is visible.
  • Use ? to redraw the main menu.
  • Use M for message bases, F for file areas, and D for doors.
  • Use X inside message, file, and door menus to return to CORE.
  • If the board disconnects, reconnect and confirm WFC answers normally.

Online modules must preserve REMMS session state. If a custom module loses the caller, review its session restore, ROPEN,0, route, and return path.

Door Is Missing

Missing doors print:

DOOR UNAVAILABLE.

Check:

  • the caller's access level meets the door catalog level;
  • the door path in the offline DOORS.CFG source ends in >;
  • D1:>DATA>DOORCAT.DAT was rebuilt after catalog edits;
  • the 16MB Mutineer ATR contains the expected D1:>DOORS> directory;
  • the runtime catalog target agrees with the bundled D1: path.

Message Or File Area Looks Wrong

  • Confirm message bases use MESG?.MET, MESG?.DAT, and MESG?.IDX.
  • Confirm file areas use FILE?.MET, FILE?.DAT, and FILE?.IDX.
  • Confirm the metadata paths point to existing files.
  • Use offline maintenance tools for rebuild/compact work.
  • Keep a backup before changing live data files.

Dropped Calls

REMMS should detect carrier loss and return to WFC. If a custom module hangs after a caller disconnects, it is probably waiting for input without polling REMMS status.

At input boundaries, caller-facing modules should call RSTAT, RTGET, or REVENT, handle structured results at or above 256, and return fatal or carrier-loss states to WFC.

Backups

Keep a clean release ATR and a separate live ATR. Back up the live ATR before:

  • complete initialization;
  • editing user files;
  • editing message or file metadata;
  • adding door catalog rows;
  • replacing text assets;
  • changing bundled door programs or data.