1. Forum
  2. FidoNet Int
  3. binkd

  • Bug in OS/2 version

    From Andrew Leary@1:320/219 to All on Mon Apr 20 05:13:45 2026
    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 Mon Apr 20 19:09:44 2026
    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 Mon Apr 20 13:45:58 2026
    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)
  • From Tommi Koivula@2:221/360 to Andrew Leary on Sat Apr 25 11:52:08 2026
    On 20.4.2026 9.13, Andrew Leary wrote:
    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.

    This sounds like a klibc bug. I solved it by adding "unixroot=x:" setting in a batch file that runs binkd. The drive X: does NOT exist.

    'Tommi

    --- FMail-lnx64 2.3.3.1-B20260425
    * Origin: news://news.fidonet.fi (2:221/360.0)
  • From Andrew Leary@1:320/219 to Tommi Koivula on Mon Apr 27 05:22:58 2026
    Hello Tommi!

    25 Apr 26 11:52, you wrote to me:

    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.

    This sounds like a klibc bug. I solved it by adding "unixroot=x:"
    setting in a batch file that runs binkd. The drive X: does NOT exist.

    I tried this, but am still having the same problem. Can you show me your batch file that runs BinkD?

    Andrew

    ---
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Tommi Koivula@2:221/360 to Andrew Leary on Mon Apr 27 13:34:24 2026
    On 27.4.2026 9.22, Andrew Leary wrote:

    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.

    This sounds like a klibc bug. I solved it by adding "unixroot=x:"
    setting in a batch file that runs binkd. The drive X: does NOT exist.

    I tried this, but am still having the same problem. Can you show me your batch file that runs BinkD?

    ===
    set unixroot=r:
    set unixroot
    start "BinkD client %_time" /n /bg binkd_client.exe -c binkd_client.cfg
    start "BinkD server %_time" /n /bg binkd_server.exe -s binkd_server.cfg
    ===

    I remembered a bit wrong! Drive r: does exist, it is a ram drive.

    But the idea is to make klibc executables not to find sh, which will be run as shell even if %comspec is there.

    This trick works in my OS/2 v4.52. I don't know about ArcaOS.

    'Tommi

    --- FMail-lnx64 2.3.3.1-B20260425
    * Origin: news://news.fidonet.fi (2:221/360.0)