1. Forum
  2. FidoNet
  3. BINKD

  • Worked on this earlier af

    From Dumas Walker@1:2320/105 to OLI on Monday, May 04, 2020 17:18:00
    You can try to spin it again and again. I already quoted the BinkleyTerm docum
    tation from 1990. But I do it again for you:

    "Note that outbound areas for domains other than your own will ALWAYS have a zo
    e extension."
    [...snip...]
    Since I started using it in 1993 the 5D BSO format hasn't changed. Only binkd vented it's own thing.

    I have both BT and binkd installed on the same machine here. Both of them
    use the same format for my outbounds, by default. I do not have to specify
    the zone extension for each zone's outbound in either config file, and shouldn't unless I want to break something.

    I can tell you that binkd is using the same format that BinkleyTerm is
    using... the zone extension, in HEX.

    Mike


    * SLMR 2.1a * This just in: Research causes cancer in rats!
    --- SBBSecho 3.11-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Oli@2:280/464.47 to Dumas Walker on Thursday, May 07, 2020 10:55:32
    Dumas wrote (2020-05-04):

    You can try to spin it again and again. I already quoted the
    BinkleyTerm docum tation from 1990. But I do it again for you:

    "Note that outbound areas for domains other than your own will ALWAYS
    have a zo e extension."
    [...snip...]
    Since I started using it in 1993 the 5D BSO format hasn't changed. Only
    binkd vented it's own thing.

    I have both BT and binkd installed on the same machine here. Both of them use the same format for my outbounds, by default. I do not have to specify the zone extension for each zone's outbound in either config
    file, and shouldn't unless I want to break something.

    I can tell you that binkd is using the same format that BinkleyTerm is using... the zone extension, in HEX.

    how do your outbound directories look like? what's the outbound config in binkd.cfg?

    ---
    * Origin: (2:280/464.47)