132
log d:\binkd\binkd.log
Found out that using the \\ will create the *.log file...so will have done this.
inbound-temp d:\\fe\\inbound\\temp
BINKD threw a fit about this line...so switched it to temp-inbound & it works.
pid-file d:\binkd\binkd.pid
Same as #1.
BINKD does start up & attempts to poll a hub when I do it manually. Here's my BINKS.LOG:
! 04 May 12:34:11 [1] binkd.cfg: 38: d:\fe\inbound\insecure: incorrect directory
! 04 May 12:35:27 [1] binkd.cfg: 39: inbound-temp: unknown keyword
04 May 12:36:48 [1] BEGIN, binkd/0.9.4 binkd.cfg
04 May 12:36:48 [2] clientmgr started
04 May 12:36:48 [1] servmgr started
! 04 May 12:37:27 [1] got signal #4.
04 May 12:39:40 [1] BEGIN, binkd/0.9.4 -P3:770/1 binkd.cfg
04 May 12:39:40 [1] creating a poll for 3:770/1@fsxnet (`i' flavour)
04 May 12:39:40 [2] clientmgr started
04 May 12:39:40 [1] servmgr started
+ 04 May 12:39:40 [3] call to 3:770/1@fidonet
04 May 12:39:41 [3] trying 219.89.83.33...
? 04 May 12:39:41 [3] unable to connect: No route to host
+ 04 May 12:40:40 [3] call to 3:770/1@fidonet
04 May 12:40:40 [3] trying 219.89.83.33...
? 04 May 12:40:40 [3] unable to connect: No route to host
! 04 May 12:40:49 [1] got signal #6.
It's a start! Where do I go from here...other than updating the version?
Thanks to everyone who helped me get this far!
ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.
--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-Beep-Beep! (21:2/147)