I have recently downloade ClamAV portable and configured it to use it from behind a proxy. When I try to download the virus definitions it does not work. It downloads upto about 4% and then there is an error shown:

ClamAV update process started at Sat Jul 19 13:52:08 2008
Connecting via proxy.upng.ac.pg
nonblock_recv: giving up due to excessive bogus loops
ERROR: Verification: MD5 verification error
Trying again in 5 secs...
ClamAV update process started at Sat Jul 19 13:54:59 2008
Connecting via proxy.upng.ac.pg
nonblock_recv: giving up due to excessive bogus loops
ERROR: Verification: MD5 verification error
Trying again in 5 secs...
ClamAV update process started at Sat Jul 19 13:57:16 2008
Connecting via proxy.upng.ac.pg

It basically continues this loop for as long as i allow it to.

How do I solve this problem

Thanks in advance

looks like the proxy is blocking the request and is returning an html page instead of the db

try to open https://database.clamav.net/main.cvd with a browser

I have downloaded the main.cvd file but how do I get my ClamWin AV to use it?

When I drag and drop the fle into the ClamWin AV interface it does not do anything

Also, the updater downloads upto 5% of the main.cvd file before coming up with the MD5 verification error, so I am sure that a html page is not returned instead of the db.

Thanks a lot for your help

so the connection gets interrupted, main.cvd should be ~ 14mb, the file downloaded by the browser is 14mb?

Thanks a lot for your help

I got it to work by downloading both the main.cvd and daily.cvd files and moving them to the db folder for the ClamWin AV.

I cannot get ClamWinPortable to update. No proxy. Thumb drive installation and using an XP Home laptop. Initial downloads of CVD files worked fine but subsequent attempts to update seems to connect (reports Main.cvd is up to date) and then just stalls. A temporary folder is created in ..\Data\DB filled with currently-dated 'Daily' files but the Daily.CVD is not updated. For comparison, I also have an installation of the "regular" ClamWin on this same machine that updates with no trouble at all so it would seem it's not a connection issue.

I've tried suggestions like hiding the Mirrors.dat file in case that was the problem but the behviour was unchanged. I've also installed ClamWinPortableDBUpdate from https://www.clamup.co.nr/ and it seems to do the same thing except that it adds a tray icon that gives me access to the stalled process so that I can abort it with Ctrl-C.

Wazzup with updating the portable ClamWin??

adTHANKSvance

A couple of releases ago, Clam changed their signature files, and perhaps ClamWin Portable hasn't incorporated the changes. Try the website to see if you can get more help.

Regards,

Thanks but I don't think that's it as I have installed PortableClamWin on another thumb drive and it updates OK.

I've tried reinstallations and only got as far as described: initial database downloads come fine and subsequent connections report only that the MAIN.CVD is up to date and a temp folder of "daily" files is created.

Anyone else either confirm difficulty updating ClamWinPortable or confirm no problem?

Just to complete the circle here, I've identified the source of my problem but don't have a "fix". I got thinking about something I just mentioned here: the fact that the updating worked on a previous thumb drive. So, I just installed the PA Suite on another drive (Kingston DataTraveler like the first one) and everything works perfectly! I especially like the interface with ClamWinPortableDBUpdate.

The ClamWinPortable updates fine using any method I've tried on Kingston DataTraveler drives (I've tried both the 1GB and 2GB so far) but not on a Lexar 4GB. Dunno what Lexar does differently -- it comes with SecureII software but I'm not using it.

So, at least for now, Lexar is off my list for Portable Apps. Anyone have success with Lexar drives?

This failure of ClamWinPortable to update only on certain drives has been intriguing/bugging me! So I've now installed PAM on a 4GB Kingston and a 1GB Lexar. And guess what: the smaller Lexar will update (as long as you're patient as it's much slower) and the larger Kingston won't! So now I have collected these data points:

2GB Kingston - updates fine
4GB Kingston - won't update
4GB Lexar - won't update
1GB Lexar - updates eventually

This suggests that ClamWinPortable will only update on smaller drives, despite the lack of logic in that.

To recap, the lack of updating seems not to be related to connectivity (all tests done on an Acer laptop, XP Home, home LAN). All connect and verify the Main file but only the smaller drives download and actually update the Dailies. The full ClamWin on the hard drive updates OK. The larger thumb drives stall after verifying the Main file and leave behind a temporary folder with a bunch of 'daily' files in it.

Can anyone add to these data points, either confirming or disproving the theory? Better still, can anyone familiar with the ClamWinPortable update process suggest a fix for this?

usb drive size it's not reasonable as explanation, I'll make some tests with clamwin portable

I've made a lot of tests with a 512mb usb key, none of these problems, I'll test a 1gb but I suspect the md5 error
is related to problems on the media, try to make a chkdsk with full sectors scan

from cmd prompt
chkdsk x: /R

still no problems with an hp 1gb and a "peak" 1gb
look also in event viewer it may say something if a disk error occurs

ps incremental update is slow as hell on a usb key

Please note my report carefully. This problem seems to occur only with LARGER USB drives (4GB at least), not smaller drives. It is not a "disk error"; it occurs with drives from different manufacturers -- Kingston & Lexar so far -- but only if 4GB (and perhaps larger, haven't tested larger than 4GB).

ClamWinPortable performs normally UP TO the point where the dailies should update but stops without that last step on my 4GB drives. 1GB and 2GB drives are no problem.

I don't have flash disks > 1G right now to test it, I suppose that usb HD are not suitable to debug this problem, right?