Hello,

So, while I was playing around with 3.44, I think I came up with a workaround
for the cache bug. According to my observation, when you terminate httrack
while mirroring is in progress, the new.zip file in hts-cache gets corrupted.

To me, it looks like there is a new entry started (just 3-4 bytes from the end
of the file).

In a properly saved new.zip cache file, there are no such bytes, just a zipped
footer like:

HTTrack Website Copier/3.44-1 mirror complete in 2 minutes 1 seconds : 102
links scanned, 12 files written (55194 bytes overall) [59288 bytes received at
489 bytes/sec]
(1 errors, 0 warnings, 121 messages)

So, here, it came to me out of blue.

What if we set maximum mirroring time limit to, let's say 3600 seconds,
so that httracks finishes the cache up cleanly.

After that, we can simply continue mirroring, with the just created cache.

I have done a few tests already and it seems to work for me.

Let me know how it turns out for you.

On the other hand, I'm considering to write some code and replace zip with
SQLite for cache,
the benefits of doing this would be huge.