Hi,
On 2016-01-25 16:10:18, Bj”rn Felten wrote to Wilfred van Velzen:
about: "BSO .try files":
WvV>> Now I noticed that binkd is writing 5 binary bytes to a try file.
WvV>> Seems like some status information, plus the following string
WvV>> length.
BF> Yes indeed binkd is using those files for some seemingly undocumented
BF> purpose.
BF> In a quick and dirty search, I found this in ftnq.c:
BF> void write_try (FTN_ADDR *fa, unsigned *nok, unsigned *nbad, char
*comment,
BF> void read_try (FTN_ADDR *fa, unsigned *nok, unsigned *nbad,
I've looked at those too, before I send the message. ;)
BF> I haven't found the time to further investigate e.g. the define for
BF> the *.try file, but if I find anything I'll keep you posted.
If I understand Pavel (in the BINKD area) correctly. The .try (and .csy) files
are "inventions" by binkd. The binkleyterm documentation doesn't mention them.
So I think the FTSC documentation might be wrong. Maybe it shouldn't even
mention the .try file, because it's not part of BSO, and only a binkd
"internal" status file.
Bye, Wilfred.
--- FMail-W32-1.69.12.144-B20160109
* Origin: Native IPv6 connectable node (2:280/464)
|