Subj : Re: 'conflicted' files
To   : Black Panther
From : g00r00
Date : Sat Nov 27 2021 02:38 pm

 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!

--- Mystic BBS v1.12 A47 2021/11/24 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.