Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Parsing /sbbs/fido/inbound/ TK990711.TIC
Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Created by NEF/pk OS/2 2.45b2
- Copyright 1991-1998 by Alberto Pasquale, 1999-2000 by Paul Kourochka
Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Path 618:618/1 1571990709 Fri Oct 25 08:05:09 2019 UTC
Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT WARNING: File '/sbbs/fido/ inbound/micronet.zip' length mismatch. File is 8210, expected 8614.
Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Parsing /sbbs/fido/inbound/ TK990717.TIC
Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Created by NEF/pk OS/2 2.45b2
- Copyright 1991-1998 by Alberto Pasquale, 1999-2000 by Paul Kourochka
Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT Path 618:618/1 1571990709
Fri Oct 25 08:05:09 2019 UTC
Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT WARNING: File '/sbbs/fido/ inbound/mininfo.zip' length mismatch. File is 19194, expected 19598.
The file length mismatch is causing the files not to be tossed, and causing my downlinks not to receive updated nodelists, etc. This seems to happen with pretty much any file from any source except my fido connection with Janis at 1:261/38.
I am guessing that is a part of the TIC standard or something, but is there a way to turn it off? These both seem to be off by 404 bytes. Not sure what would cause that (different OSes, the transfer protocol used by binkp/binkit, etc.), but it is not at all a difference that I am worried about so I would really prefer that tickit would ignore this error and go
on about its business.
I was able to comment out a few lines in tickit.js (after copying to /mods) and now it ignores the file length mismatch. I would guess maybe that is not good, for some reason, in all cases?
Dec 28 18:09:34 hooray4 synchronet: evnt TICKIT WARNING: File '/sbbs/fido/inbound/mininfo.zip' length mismatch. File is 19194, expected 19598.
Are the received files okay (e.g. the CRCs match, they pass zip verification)?
It would be pretty odd for the CRCs to match, but the lengths not to. I can't t
ink of an explanation for that one. If the files were modified (e.g. zip commen
s replaced or stripped) after the .tic file was generated, then I would expect >he file CRC to be different as well (and not match the value in the .tic file).
I am not 100% sure, but I think that tickit is not deleting the *.TIC filesafter it processes them
you really need to find out why those files are not the same size as the TIC sa
s they should be... something on the sending end is not right...
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 28 |
Nodes: | 8 (0 / 8) |
Uptime: | 190:52:49 |
Calls: | 2,006 |
Calls today: | 3 |
Files: | 11,114 |
Messages: | 942,286 |