> Sorry. This issue has already been discussed too many 
times 
> it appears. The only reason I was confused was because 
> the 'Continue interrupted download' function also used to 
> scan, and this 'scanning' takes too much time, even for 
> smaller archives, it almost looks like it's looking for 
> updates. 

Err, the problem is when you have thousands or tens of 
thousands links ; the continue feature may then be taking 
some time ; but it should be quite fast anyway (the only 
slow thing might be "404" errors)

Humm, maybe I should NOT retest "404" pages and other error 
pages during a continue?