That’s the same thing I just thought. But I don’t think mystic will even
open mystic.dat if it can’t write to it.

I’d check permissions - lots of people are using Linux and windows A39

On 06:03 10/11 , Todd Yatzook wrote:
>On 11/10/18, Ib Joe said the following...
> 
> IJ>  DR> It's something that caught a lot of us off-guard...
> IJ> 
> IJ> I did that... I have found and install copy of A35 and it works, to have
> IJ> a FTN address, I upgrade to A39 I cannot put one in where it saves. I
> IJ> did a fresh install of A39, same thing.  I just found a copy of the A35
> IJ> hanging around and it works fine, I can add a FTN address in.
>
>Is it running on Linux, and have you recursively changed ownership/execution
>of the entire directory and files within? It might be one/both of those. a35
>might be using a different data file to store the addresses, which might
>already have rwx and ownership.
>
>--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
>

-- 
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Linux/64)