Have things working but noticed every now and then a file is not processedbecause a
CRC was expected and it didn't match. One specifically is the z1dailyfiles and I
checked it and it is good.
So question is this, besides manually placing the file in sbbs, is there away to
bypass, add an exeception, etc so tickit will process it?
Have things working but noticed every now and then a file is not processed because a CRC was expected and it didn't match. One specifically is the z1daily files and I checked it and it is good.
So question is this, besides manually placing the file in sbbs, is
there a way to bypass, add an exeception, etc so tickit will process
it?
Do you have some output from TickIT (a log message) mentioning this CRC error that you can share? Can you post the file somewhere so we can check it out?
How did you check the file to confirm that it's good? Extracted it and inspected visually?
processed because a
CRC was expected and it didn't match. One specifically is the z1daily files and I
checked it and it is good.
Do you have some output from TickIT (a log message) mentioning this CRC error that you can share? Can you post the file somewhere so we can check it out?
I ran jsexec tickit and I saw screen output. It was the only file and thelast thing said it
expected a specific CRC but got something else instead (a different CRC)
Sysop: | Zazz |
---|---|
Location: | Mesquite, Tx |
Users: | 7 |
Nodes: | 4 (0 / 4) |
Uptime: | 14:33:48 |
Calls: | 157 |
Files: | 2,103 |
Messages: | 144,386 |