Hi Paul,   
      
   On 25 Jul 17 17:18, Paul Quinn wrote to Wilfred Van Velzen:   
     about: "Re: Status check":   
      
    PQ>>> On the other end of the scale, I have a test bed   
    PQ>>> Puppy (linux v2.6.x.x) VirtualBox waiting while I'm   
    PQ>>> working slowly through an FM config in an old XP VirtualBox.  :)   
      
    WvV>> Do those two virtual box's use common drive space? (Then   
    WvV>> you're ready ;))   
      
    PQ> Nope.  Na'er the twain meets, except via IP.  OTOH, one VM has a drive   
    PQ> letter, a colon, and path(s) with slants thusly "\", while the other has   
    PQ> the same path(s) with "/" slants.  A simple command-line argument will fix   
    PQ> that, you say...  ;-)   
      
   I said that wrong. It's an environment variable you have to set. ;)   
   If that is set the drive letter plus colon is replaced with the contents of   
   the environment variable and "\"'s are converted to "/"'s in the configuration   
   paths.   
      
   However FConfigW32 checks and creates paths when you configure them, so it   
   would be much easier if it does that on the "shared" drive were the real files   
   exist. So you don't have to create them by hand on the linux drive, and copy   
   over the configuration files, with the chance you make mistakes, every time   
   you change something in the config.   
      
    PQ> While I have your attention: how much RAM would be recommended for   
    PQ> Fmail/linux?  (The intended working Puppy vBox has been humming for six   
    PQ> years with 256Mb, running binkD, CM II, GoldEd and JamNNTPd, and, rarely   
    PQ> ever uses half of it.)  Too early to say yet?  Then say so.  :)   
      
   FMail uses the most memory when it calls the JAMmaint function. It does that   
   when messages are tossed into a Jam area, and you have 'Update reply chains'   
   configured to 'Yes', or when the 'FTools Maint' command is used. It will at   
   least use twice as much memory as the combined size of the 4 files that make   
   up a Jam area. So memory usage will depend on your largest Jam area.   
      
   Everything else is in the kilobyte range or maybe lower megabyte range, so   
   more or less neglectable, I suspect, because I've never measured this. ;)   
      
   Wilfred.   
      
   --- FMail-W32 2.0.1.4   
    * Origin:  point@work  (2:280/464.112)