I get the following messages when downloading - how can I correct

15/12/2009 04:13:28 PM malariacontrol.net Started download of torso.png
15/12/2009 04:13:28 PM malariacontrol.net Started download of wu_679_173_259493_0_1260885736
15/12/2009 04:13:29 PM malariacontrol.net Incomplete read of 800.000000 < 5KB for torso.png - truncating
15/12/2009 04:13:29 PM malariacontrol.net Finished download of torso.png
15/12/2009 04:13:29 PM malariacontrol.net Started download of wu_679_176_259493_0_1260885736
15/12/2009 04:13:29 PM malariacontrol.net [error] File torso.png has wrong size: expected 144871, got 0
15/12/2009 04:13:29 PM malariacontrol.net [error] Checksum or signature error for torso.png

____________

Go to your project preferences and change the option:
Skip image file verification? from no to yes

Then update your preferences in the BOINC client and see if that helps.

Unfortunately no joy - I checked the "skip image file verification" box under advanced preferences but still get the checksum error and failed download of the task

Are you going through any kind of proxy? Does http://whatismyipaddress.com/ tell you anything useful about proxies you may not be aware of?

Alternatively, do you know if there is any application on your pc (av scanner maybe?) that may be intercepting your http traffic and truncating it?

You can also try pasting the url to the file in question directly into your browser and see what happens. The url for the file you mentioned is: http://www.malariacontrol.net/download/torso.png

If this works, you can get the other urls from the client_state.xml file in your boinc directory, but you may still have problems doing scheduler request/response traffic until you find the base cause of this problem.

Thanks for the advice - I am working thorugh a proxy and it appears to be the problem. What ? I have no idea. I tried on 3G and had no issues everything went fine - that is the route I will follow in the short term.
Thanks

Thanks for the advice - I am working thorugh a proxy and it appears to be the problem. What ? I have no idea. I tried on 3G and had no issues everything went fine - that is the route I will follow in the short term.
Thanks