27 Mar 20 09:31, you wrote to me:

 ml>   Re: Issue with BinkD and outbound attempts.
 ml>   By: Oli to mark lewis on Fri Mar 27 2020 14:15:17


 >>   c:\bink\outbound        (Default Outbound)
 >>   c:\bink\outbound.002    (FidoNet Zone 2)
 >>   c:\bink\outbound.003    (FidoNet Zone 3)
 >>   c:\bink\outbound.004    (FidoNet Zone 4)
 >>   c:\bink\amiganet.027    (Amiganet Zone 39)
 >>   c:\bink\agoranet.02e    (Agoranet Zone 46)
 >>   c:\bink\dbnet.0c9       (Dbnet Zone 201)

 ml> this is exactly what i'm speaking of... my understanding is that proper 5D
BSO
 ml> for the above should be

 ml>   c:\bink\outbound        (Default Outbound)
 ml>   c:\bink\outbound.002    (FidoNet Zone 2)
 ml>   c:\bink\outbound.003    (FidoNet Zone 3)
 ml>   c:\bink\outbound.004    (FidoNet Zone 4)
 ml>   c:\bink\amiganet        (Amiganet Zone 39)
 ml>   c:\bink\agoranet        (Agoranet Zone 46)
 ml>   c:\bink\dbnet           (Dbnet Zone 201)

 ml> 4D BSO would have ALL of them named "outbound.xxx" like this...

 ml>   c:\bink\outbound        (Default Outbound)
 ml>   c:\bink\outbound.002    (FidoNet Zone 2)
 ml>   c:\bink\outbound.003    (FidoNet Zone 3)
 ml>   c:\bink\outbound.004    (FidoNet Zone 4)
 ml>   c:\bink\outbound.027    (Amiganet Zone 39)
 ml>   c:\bink\outbound.02e    (Agoranet Zone 46)
 ml>   c:\bink\outbound.0c9    (Dbnet Zone 201)


 ml> what you posted above is what i'm calling 4.5D since it is a mixture of 4D
and
 ml> 5D...

What you call 4.5D is what I know as 5D from the 1990s. IIRC Squish and
Binkleyterm use the hex extension for all outbound dirs that are not the
default outbound.

The example I posted was a quote from FTS-5005
http://ftsc.org/docs/fts-5005.003

Which tossers do support 5D.nohex binkD style outbound?


--- GoldED+/LNX 1.1.5-b20180707