Hi Nicholas,   
      
   On 14 Aug 17 17:42, Nicholas Boel wrote to Wilfred van Velzen:   
     about: "Argh!":   
      
    WV>> I just tested on a Windows 10 Pro 64bit machine. Put FConfigW32.exe   
    WV>> in an empty directory, started it, changed the 'Max exports' setting   
    WV>> (to different values: 65, 128, 256. Closing FConfigW32.exe after each   
    WV>> setting, and restarting it. There were no crashes and the value set   
    WV>> was preserved, after closing and starting the exe...   
      
    NB> As per your previous message also, yes. Same date, time, and file size.   
      
    NB> Other than that, I have no idea why it's only doing it for me then. I'm   
    NB> not using Pro, just whatever the home version is (free upgrade). I also   
    NB> tried moving FConfigW32.exe to it's own empty directory and had the same   
    NB> issue. Even tried running it as administrator with the same results. I'm   
    NB> at a loss.   
      
   I don't think it has anything to do with the windows version.   
      
   Have you set the FMAIL environment variable?   
      
   What kind of machine are you running it on? Processor; Ram; ...   
      
   Can you test it on another machine (in an empty directory).   
      
      
   Wilfred.   
      
   --- FMail-W32 2.0.1.4   
    * Origin:  point@work  (2:280/464.112)