> Thanks, I realize that. However, I was talking about
> the GUI version. To illustrate HTTrack's odd stance,
> image there being a command-line version of each of
> Internet Explorer, Mozilla, Firefox and Netscape, that
> runs faster and has more capability than the respective
> GUI version.

bk, there is a "hidden" feature in WinHTTrack that command-line arguments can
be inserted in the scan rules box. For example we put -N1001 in there to
override the build structures available in the GUI.

I think the recent additions of limits is a good thing.  There was a time when
HTTrack had NO default restrictions on speed and connections and I made Xavier
put them in :p  Obviously still it is too 'easy' to remove sensible
restrictions by people who might not understand what they're doing.  For
people who do, those options are still available.

Also don't understand your "kiloByte-Connections per sec". You could say 250
kBC/s = 1kB/s and 250 connections which would effectively nuke a server. 
Speed is nice of course but more connections can/will slow a server down when
it has to allocate resources or do processing.