"David H. Lipman" wrote in
:

WGET will work as fast as the bandwidth allows. It also can emulate any
User-Agent and Referrer string.

Nothing can replace WGET. I use...
GNU Wget 1.13.1 built on mingw32.



Hell yeah, I'd never throw it out.
I use this in a batch file:
SET UA="Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR
1.1.4322)"

Never needed the referrer, though I imagine some pages demand one to match
their expectations. Usually better to have none, as most just look for ANY
referrer as proof of offsite linkage.

I noticed that Easynews connectionc can start slowly, and if they do not rise
to about 300 KB/s they'll fall to around 42 KB/s and not recover. When I'm
impatient I abort, and restart WGET. (Using -c to continue, resume...) I
haven't looked at WGET in enough detail to see if it can detect this problem
and auto-retry to persist in seeking fast server lines, but if it can, it
proves itself yet again. For some things, multisegment down load is crucial
though. The problems solved by that are easily solved by any program that can
download multiple files, but if ONE big file is causing trouble,
multisegmenting is the only way to get multiple lines to that file. As far as
I know, WGET can only do one line at a time, no matter what. But I often use
up to four instances, each with its own list. That makes fast work most
times on Easynews...