Subj : Binkd with Fastecho...
To   : Nick Boel
From : Oli
Date : Tue Dec 03 2024 05:37 pm

Nick wrote (2024-11-30):


NB> Don't overthink this. When using 1 for each of the above domains, binkd
NB> will automatically look in the outbound.xxx directories that Fastecho is
NB> creating. It will not "put all of the directories together", binkd
NB> automatically uses the hex value for the directory extensions when you
NB> use 1 for the zone.

NB> If Fastecho was /really/ doing 5d, it wouldn't have directory extensions
NB> (which binkd does correctly when you use the above settings), but it's
NB> not.

No, unfortunately binkd is doing it wrong by default. Fastecho implements 5D BSO correctly according to the FTSC standard.
And yes, using a non-existing zone (e.g. 1) as the default zone for the domain is a proper workaround.

---
* Origin: No REPLY kludge - no reply (2:280/464.47)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.