Using the command line httrack (ver 3.30+swf) under Windows
2000 SP4, I've noticed that a "httrackrc" file in the
current directory will not be parsed if it does not contain
a path parameter.

For example, my "httrackrc" file contains the following:

  near on
  sockets 10
  retries 10
  host-control 0

Since it does not contain a path parameter, I invoke httrack
like this:

  httrack <http://somesite.com/> -O "c:\temp\somesite" 

"doit.log" in C:\temp\somesite\hts-cache shows these parameters:

  <http://somesite.com/> -O "c:\\temp\\somesite" 

But after updating "httrackrc" to look like this

  near on
  sockets 10
  retries 10
  host-control 0
  path "C:\temp\somesite"

and invoking httrack like this

  httrack <http://somesite.com/>

"doit.log" shows these parameters

  -n -c10 -R10 -H0 -O "c:\temp\somesite" <http://somesite.com/>

I was under the impression that "httrackrc" acts as a set of
user defined defaults, overriding some or all of the program
defaults.  Has anyone else experienced similar results under
Windows?  Is this behaviour consistent for all operating
systems?
Cheers,
Jason.