inbound c:\binkd\in
And this directory exist into my DOS system.
I have recently downloaded binkd for DOS, and am experiencing the following
issue:
When I try to run the command:
binkd -P 4:801/188 binkd.cfg
I get the following error message:
21:51 [2026] binkd.cfg: line 134: error in configuration files
21:51 [2026]inkdin: incorrect directory
21:51 [2026] error in configuration, aborting
Line 134 from my binkd.cfg file has:
inbound c:\binkd\in
And this directory exist into my DOS system.
Is there anything special regarding the inbound directory?
Hello Flavio!
04 Feb 21 21:59, you wrote to all:
I have recently downloaded binkd for DOS, and am experiencing the following
issue:
When I try to run the command:
binkd -P 4:801/188 binkd.cfg
I get the following error message:
21:51 [2026] binkd.cfg: line 134: error in configuration files
21:51 [2026]inkdin: incorrect directory
21:51 [2026] error in configuration, aborting
Line 134 from my binkd.cfg file has:
inbound c:\binkd\in
And this directory exist into my DOS system.
Is there anything special regarding the inbound directory?
Backslashes in the configuration file are used as escape characters. You need to specify 2 backslashes to do what you want to do.
ie:
inbound c:\\binkd\\in
Backslashes in the configuration file are used as escape
characters. You need to specify 2 backslashes to do what you want
to do.
ie:
inbound c:\\binkd\\in
Or use foward-slashes (e.g. c:/binkd/in) - yes, it works fine in DOS.
Backslashes in the configuration file are used as escape characters.
You need to specify 2 backslashes to do what you want to do.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 409 |
Nodes: | 16 (2 / 14) |
Uptime: | 67:07:49 |
Calls: | 8,575 |
Calls today: | 5 |
Files: | 13,225 |
Messages: | 5,930,970 |