| Actually this was on Win2k, in a Remote Admin Terminal
Server session. I like to run long jobs like web copying
on my server so my laptop isn't tied up for extended
periods.
I guess the other thing I can try is extracting the
WinHttrack files into another folder and run them from
there (with your customized winhttrack.exe module).
Are there any memory usage conditions where WinHttrack will
bomb-out that you know of? I regularly see it consuming 50-
100mb RAM on large grabs, but that shouldn't be a problem
in this server as it has a 208mb RAM + 1gb dedicated swap. | |