log d:\binkd\binkd.log
inbound-temp d:\\fe\\inbound\\temp
pid-file d:\binkd\binkd.pid
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
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?
Yep, dunno where you got that from but get it outa there.. ;)inbound-temp d:\\fe\\inbound\\tempBINKD threw a fit about this line...so switched it to temp-inbound & it works.
temp-inbound is what you want.
04 May 12:36:48 [1] BEGIN, binkd/0.9.4 binkd.cfgI 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?
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?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 60:39:58 |
Calls: | 6,488 |
Calls today: | 1 |
Files: | 12,094 |
Messages: | 5,274,354 |