On Tuesday 07 February 2006 11:04, Victor Lazzarini wrote:

> It was indeed corrupt. I have updated it now and I've downloaded, gunzipped and
> untarred it, so it's all OK. I'm not sure what it was, but I don't think 
> that was due to ASCII encoding, as I used binary both times.

If by both times you also mean the 10.3 and 10.4 packages before the
Feb 01 release, then those were indeed very likely to be corrupted by
binary to ASCII conversion. The files had all byte values evenly distributed
(as one would expect from a gzipped file), but 0x0D (CR) occured about
twice as often as the others. Also, the fixed files were smaller by about
0.35% which is close to 1/256 (again suggests having a specific byte
value replaced by two bytes).
Of course, I have not downloaded the 10.2 package, so I was only guessing
about that.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net