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: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 104 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 01:31:50 |
| Calls: | 7,094 |
| Files: | 9,223 |
| D/L today: |
138 files (17,200K bytes) |
| Messages: | 373,564 |