Subj : Re: Bink D --- HELP!!! Don't know what I'm missing
To : Tony Langdon
From : Bill McGarrity
Date : Tue Nov 07 2017 06:26 am
-=> Tony Langdon wrote to Bill McGarrity <=-
-=> Bill McGarrity wrote to Alprunty <=-
-=> Alprunty wrote to echicken <=-
Al> Re: Bink D --- HELP!!! Don't know what I'm missing
Al> By: echicken to Alprunty on Fri Apr 22 2016 08:45 pm
> 'c:\\sbbs\\bink\\binkd.log' or 'c:/sbbs/bink/binkd.log'.
Al> Why are we double slashing?
BM> binkd uses a linux style cfg file which doesn't have the same directory
BM> structure as a win based system.,... therefore the double slash when
BM> using backslashes. Trust us, it works.. :)
TL> Looks like binkd interprets its config in a similar way to shells such
TL> as Bask, so the first backslash is an escape character, the second
TL> tells the parser that the character to read is a backslash. Those of
TL> us familiar with mixing Windows and Linux will have seen this before.
TL> For example, when mounting SMB/CIFS shares on a Linux box.
Yup. The instruction within the the cfg file actually state for WIN systems
the couble backslash is needed.
