> > error log said something like "incorrect file size
> 
> Weird - the disconnection should have been logged. I'll 
> check that for the next release (maybe a bad error 
handling)
> 
> > any longer than before, but still claimed to 
fail "after 
> > 999 retries".
> 
> If the network connection failed, the retries will all 
fail 
> (there is no delay between retries yet)

Yes, but if/when the connection for file X fails, it moves 
on to file X+1, on to the end, and then, if "retries" 
hasn't been exceeded yet, makes another stab at any of 
files 1 through X-1 that haven't been caught yet before 
retrying file X.  I was watching the whole time, and would 
have noticed if it had ended with a flurry of meaningless 
activity like you suggest.  This leads me to believe that 
the root cause is not with the physical connection, but 
probably at the server end.

However, this doesn't mean that HTTrack can't do a better 
job of picking up where it left off, regardless of the 
cause of the interruption.  In fact, I'm going back to the 
older version, which I found was 3.22-3, because it does 
seem better at this.  After leaving the new version running 
for several hours, most of the partially downloaded files 
are now actually *smaller* than they were before - which 
IMO should never happen!

Oh, and BTW, I left comments/bug reports in two other 
threads, which you should probably also check:

<http://forum.httrack.com/readmsg/8560/8555/index.html>
and
<http://forum.httrack.com/readmsg/8556/8496/index.html>

Thank you for your quick response.