You can try to spin it again and again. I already quoted the BinkleyTerm docum[...snip...]
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."
Since I started using it in 1993 the 5D BSO format hasn't changed. Only binkd vented it's own thing.
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[...snip...]
have a zo e extension."
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.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,039 |
Nodes: | 15 (1 / 14) |
Uptime: | 109:19:59 |
Calls: | 236,257 |
Calls today: | 2 |
Files: | 95,022 |
D/L today: |
3,373 files (355M bytes) |
Messages: | 290,680 |