> The only problem is that I am not totally sure that the 
> whole httrack code is protected against 'int overflows' 
> (some parts still contains code like 'int size = foo.. 
fseek
> (..,size)')

Okay, I checked, and another problem are hash tables: 
internal hash tables used by the cache are "unsigned long 
int" format, not comaptible with __int64.

The new.dat file format IS 64-bit ready (even more, as all 
indexes are serialized using decimal strings), but internal 
httrack structure aren't yet.