search for: zero_retri

(Erm, sorry about that...) I was talking about errors of the type: Got 0 bytes. The problem was sporatic, and seemed to be load/speed based. That is, the faster the Linux box, the more errors we had. A look through clitar.c led me to a solution. Currently, clitar.c is written to pad a file with zeros if a file read error occurs. This is normal. All of our errors were of the 0 byte length