Just curious, what made the dat file require executable privileges? Was
it just a check to see if it had correct privileges that had the wrong mode or something?
It's got me intrigued lol :)
I had it setup to check "mystic" for READ/WRITE/EXEC privileges. I decided to change that to MYSTIC.DAT considering if the program is already running you know they probably have /read/exec at least... And none of that matters if
it can't get the configuration from MYSTIC.DAT.
The problem was I changed "mystic" to "mystic.dat" but I forgot to remove the code that checked the +X attribute.
--- Mystic BBS v1.12 A39 2018/04/16 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)