From: nospam.g00r00@f215.n129.z1.fidonet.org   
      
    BP> I'm currently working on updating a MPL from a few years ago, and it   
    BP> keeps it own log file. The log file is now getting renamed to   
    BP> 'conflicted'.   
    BP>   
    BP> unopened? Is this a general 'catch-all' type of event that happens when   
    BP> there is an error somewhere? It would just give me somewhere to start   
    BP> looking for the problem. :)   
      
   There is nothing in Mystic that does this that I can think of anyway.  Are you   
   using a networked file share of some sort that could be doing this while there   
   are conflicts in files?  Or a VMware with shared directories or anything like   
   that?   
      
   ... As a matter of fact, it IS a banana in my pocket!   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)