1. Forum
  2. FidoNet
  3. SYNC PROGRAMMING

  • docs/v322_new.md src/sbbs3/xtrn_sec.cpp

    From Rob Swindell (on Debian Linux)@1:103/705 to Git commit to main/sbbs/master on Sun Aug 9 23:03:12 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/2c49eafa1f3c5bfce980fbe4
    Modified Files:
    docs/v322_new.md src/sbbs3/xtrn_sec.cpp
    Log Message:
    Report GR in DOOR.SYS line 20 whenever ANSI is supported

    Line 20 required both ANSI and COLOR, so a caller using an ANSI
    terminal in monochrome mode was told "NG" and doors ran with ANSI
    disabled entirely.

    The monochrome distinction belongs to line 39 ("ANSI supported but
    NG mode"), which is still computed, but no door kit consults it.
    OpenDoors and xpdoor (both in this tree), MBSE's doorlib, and the
    Turbo Pascal DoorDriver Plus kit all decide ANSI solely from line
    20 -- DoorDriver Plus closes the file immediately after reading it,
    and doorlib names line 39 "allwaysN". Writers agree: WWIV emits GR
    on ANSI alone, and the published field definitions describe line 39
    as "always set to N".

    The ANSI-plus-COLOR test dates to the initial v3.00c check-in and
    was never revisited. 554c2ca395 (days-21-coins, 2020-12-11) moved
    it from useron.misc to the negotiated terminal flags for this same
    symptom -- doors losing ANSI for an ANSI-capable caller -- but kept
    the COLOR requirement.

    Affects both the 52-line and 31-line drop-file forms; line 20 is in
    the section common to both.

    Closes #1218

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell (on Debian Linux)@1:103/705 to Git commit to main/sbbs/master on Wed Sep 30 19:08:47 2026
    https://gitlab.synchro.net/main/sbbs/-/commit/173a186e70b43fde72488d35
    Modified Files:
    docs/v322_new.md src/sbbs3/xtrn_sec.cpp
    Log Message:
    DOOR.SYS: derive the caller-alarm field as PCBOARD.SYS does

    Fixes #1251

    The DOOR.SYS writer hardcoded field 9 ("caller alarm") to Y, while the PCBOARD.SYS writer sets its alarm from whether an answer sound is
    configured and ctrl/sound.mute is absent. The same sysop setting therefore reached a door or not depending only on which drop-file format the door
    was configured for. Use the PCBOARD.SYS expression for DOOR.SYS too.

    Verified with a scratch external that copies its DOOR.SYS out: field 9 is
    Y with an answer sound configured and N once sound.mute exists.

    Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
    --- SBBSecho 3.38-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)