Hi! Wilfred,

On Tue, 25 Jul 17, you wrote to me:

 PQ>>  A simple command-line argument will fix that,
 PQ>>  you say...  ;-)

 WvV> I said that wrong. It's an environment variable you have
 WvV> to set. ;)

No problem.  I can do them too.

 WvV> If that is set the drive letter plus colon is replaced with
 WvV> the contents of the environment variable and "\"'s are
 WvV> converted to "/"'s in the configuration paths.

Ah-huh.  Sweet.

 WvV> However FConfigW32 checks and creates paths when you
 WvV> configure them, so it would be much easier if it does that
 WvV> on the "shared" drive were the real files exist. So you
 WvV> don't have to create them by hand on the linux drive, and
 WvV> copy over the configuration files, with the chance you
 WvV> make mistakes, every time you change something in the
 WvV> config.

Mistakes... nah, ain't gonna happen.  I'm a profeesioanl anatuer.  ;-)

 WvV> FMail uses the most memory when it calls the JAMmaint
 WvV> function. It does that when messages are tossed into a Jam
 WvV> area, and you have 'Update reply chains' configured to
 WvV> 'Yes', or when the 'FTools Maint' command is used. It will
 WvV> at least use twice as much memory as the combined size of
 WvV> the 4 files that make up a Jam area. So memory usage will
 WvV> depend on your largest Jam area.

Not a problem.  The biggest area currently is BinkD, at ~20Mb.  There
again, I'll be starting off the Fmail/Linux environment from scratch.

 WvV> Everything else is in the kilobyte range or maybe lower
 WvV> megabyte range, so more or less neglectable, I suspect,
 WvV> because I've never measured this. ;)

:)  Nice to know.  Thank you, kindly.

Cheers,
Paul.

--- Paul's Win98SE VirtualBox