Windows 7 and BinkD

[Paul Quinn]

+ CrossPosted in: WINDOWS
+ CrossPosted in: BINKD


Hi! Janis,

In a message to All you wrote:

JK> The error he's seeing on his win box is
JK> The system cannot find the path specified.

JK> Very frustrating because the path is correct as far as I know in his
JK> binkd.cfg file ("\\pcx\\binkd\\) etc.

JK> He sees the above error when he tries to poll here with
JK> binkd -P1:261/38 binkd.cfg

It could simply be a matter of the 'case' of the argument for that release.
Tell him to try it with "binkd -p1:261/38 binkd.cfg" instead.

Cheers,
Paul.

... We see what we look for and we look for what we think we will see. jms

[Nicholas Boel]

On 05-13-14, Paul Quinn said the following...

PQ> JK> He sees the above error when he tries to poll here with
PQ> JK> binkd -P1:261/38 binkd.cfg
PQ>
PQ> It could simply be a matter of the 'case' of the argument for that
PQ> release. Tell him to try it with "binkd -p1:261/38 binkd.cfg" instead.

Oh wait now..

Make sure you either put a "./" at the beginning of the executable to run, or
the path to it, ie:

./binkd -P1:261/38 binkd.cfg

or

/path/to/binkd -P1:261/38 /path/to/binkd.cfg

Regards,
Nick

[Janis Kracht]

Hi again,

Post by Nicholas Boel

Post by Paul Quinn
JK> He sees the above error when he tries to poll here with
JK> binkd -P1:261/38 binkd.cfg
It could simply be a matter of the 'case' of the argument for that
release. Tell him to try it with "binkd -p1:261/38 binkd.cfg" instead.

Oh wait now..
Make sure you either put a "./" at the beginning of the executable to run, or
./binkd -P1:261/38 binkd.cfg
or
/path/to/binkd -P1:261/38 /path/to/binkd.cfg

Yep, good idea... never hurts to be specific, thanks :)

Take care,
Janis

[Janis Kracht]

Hi Paul,

Post by Paul Quinn

Post by Paul Quinn
The error he's seeing on his win box is
The system cannot find the path specified.
Very frustrating because the path is correct as far as I know in his
binkd.cfg file ("\\pcx\\binkd\\) etc.
He sees the above error when he tries to poll here with
binkd -P1:261/38 binkd.cfg

It could simply be a matter of the 'case' of the argument for that release.
Tell him to try it with "binkd -p1:261/38 binkd.cfg" instead.

As I mentioned in the WINDOWS echo, I think P and p serve two different
functions, I know the version I run here does <g>.. I'll have him print out the
command list for the version that Pavel compiled that I sent him...

Thanks Paul :)

Take care,
Janis