1. Forum
  2. FidoNET
  3. BINKD

  • Bug in OS/2 version

    From Andrew Leary@1:320/219 to All on Monday, April 20, 2026 05:13:45
    Hello everybody!

    While testing external file request processors on my OS/2 system, I discovered that SRIF support has apparently been broken for a while. The issue is that the command line to execute is logged correctly, but when the call actually gets made to execute it, all backslashes (\) in the *S macro have mysteriously vanished, causing the external request processor to fail to find the SRIF file. I tested with both ALLFIX and VIREQ, and the same problem happens with both.

    This used to work in the old 1.0a-446 OS/2 version, but it's broken in every 1.1a for OS/2 version that I've tested from -68 up to -115.

    Andrew

    ---
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Kees van Eeten@2:280/5003.4 to Andrew Leary on Monday, April 20, 2026 19:09:44
    Hello Andrew!

    20 Apr 26 05:13, you wrote to All:

    While testing external file request processors on my OS/2 system, I discovered that SRIF support has apparently been broken for a while. The issue is that the command line to execute is logged correctly, but when the call actually gets made to execute it, all backslashes (\) in the *S macro have mysteriously vanished, causing the external request processor to fail to find the SRIF file. I tested with both ALLFIX and VIREQ, and the same problem happens with both.

    This used to work in the old 1.0a-446 OS/2 version, but it's broken in every 1.1a for OS/2 version that I've tested from -68 up to -115.

    Have you tried "\\" double backslashes. Maybee you will even need "\\\"
    With one "\" is the following character removed as well?

    Regards

    Kees

    Kees

    --- GoldED+/LNX 1.1.5--b20180707
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Andrew Leary@1:320/119 to Kees van Eeten on Monday, April 20, 2026 13:45:58
    Hello Kees!

    Monday April 20 2026 19:09, Kees van Eeten wrote to Andrew Leary:

    This used to work in the old 1.0a-446 OS/2 version, but it's
    broken in every 1.1a for OS/2 version that I've tested from -68
    up to -115.

    Have you tried "\\" double backslashes. Maybee you will even need
    "\\\" With one "\" is the following character removed as well?

    The *S macro is populated by BinkD itself. It logs the proper command line, but what actually gets executed has no backslash characters in it.

    Andrew

    ---
    * Origin: Bits & Bytes BBS * telnet://bbs.bnbbbs.net:2023 (1:320/119)