= Сообщение: 3124 из 7127 ====================================== FTSC_PUBLIC = От : Bill McGarrity 1:266/404 07 Nov 17 06:26:11 Кому : Tony Langdon 07 Nov 17 06:26:11 Тема : Re: Bink D --- HELP!!! Don't know what I'm missing FGHI : area://FTSC_PUBLIC?msgid=4100.2ftscpubl@1:266/404+1b816067 На : area://FTSC_PUBLIC?msgid=1660.fido-syncsyso@3:633/410+1b806e0b = Кодировка сообщения определена как: ASCII ================================== ============================================================================== -=> 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.
