Request range:
Problem detected: these files were complete, but for 
an unknown reason httrack did not store them in the 
cache, and therefore tried the next mirror to complete 
them. And this caused an error, because IIS can 
not "understand" empty request-ranges, which should be.
I'll try to implement a fix for this problem asap!

> I stand (partially) corrected:
> Modifications to a value of 1500 are displayed 
> correctly.
> Modifications to 1000 are displayed as 100000.
> Max rates are obeyed in both cases.

Yes.. because even if you type "10", the Windows GUI 
will (stupidely) attemps to find the nearest default 
suggested values (here, 100000)
This is stupid, but as far as everything is handled by 
the MFC classes, I can not really fix it..