Subj : Updated BINKD.CFG
To   : Phoobar
From : Al
Date : Mon May 04 2020 01:54 pm

Hello Phoobar,

 Ph>> log d:\binkd\binkd.log

 Ph> Found out that using the \\ will create the *.log file...so will have
 Ph> done this.

 Ph>> inbound-temp d:\\fe\\inbound\\temp

 Ph> BINKD threw a fit about this line...so switched it to temp-inbound &
 Ph> it works.

Yep, dunno where you got that from but get it outa there.. ;)

temp-inbound  is what you want.

 Ph>> pid-file d:\binkd\binkd.pid

 Ph>   04 May 12:36:48 [1] BEGIN, binkd/0.9.4 binkd.cfg

I remember that version, that's an oldie but a goodie!

I'm going to plonk BINKD104.ZIP in your inbound at 1:340/1000. Try that maybe?

 Ph>   04 May 12:36:48 [2] clientmgr started
 Ph>   04 May 12:36:48 [1] servmgr started
 Ph> ! 04 May 12:37:27 [1] got signal #4.

 Ph>   04 May 12:39:40 [1] BEGIN, binkd/0.9.4 -P3:770/1 binkd.cfg
 Ph>   04 May 12:39:40 [1] creating a poll for 3:770/1@fsxnet (`i' flavour)
 Ph>   04 May 12:39:40 [2] clientmgr started
 Ph>   04 May 12:39:40 [1] servmgr started
 Ph> + 04 May 12:39:40 [3] call to 3:770/1@fidonet
 Ph>   04 May 12:39:41 [3] trying 219.89.83.33...
 Ph> ? 04 May 12:39:41 [3] unable to connect: No route to host
 Ph> + 04 May 12:40:40 [3] call to 3:770/1@fidonet
 Ph>   04 May 12:40:40 [3] trying 219.89.83.33...
 Ph> ? 04 May 12:40:40 [3] unable to connect: No route to host
 Ph> ! 04 May 12:40:49 [1] got signal #6.

 Ph> It's a start! Where do I go from here...other than updating the
 Ph> version?

That's odd.. the above all looks good. I just polled 3:770/1 without issues. I'm going to send you a very upto date binkd in a minute here. You could try that. It's for OS/2. What OS is this running on?

 Ttyl :-),
         Al

--- GoldED+/LNX
 * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

.