Are there people having the same problem I've had, it doesn't make sense to me. If I run mystic Alpha 35, the version I ran for some time... the BBS worked fine. I updated to the current version Alpha 39 and now I cannot have my fidonet, or any any FTN address, be saved...
Is anyone having problems, or is there something I'm over looking??
Is anyone having problems, or is there something I'm over
looking??
Try setting the address in the second space down. The first one is reserved for a local address.
It's something that caught a lot of us off-guard...
Is anyone having problems, or is there something I'm over looking??
Try setting the address in the second space down. The first one is reserved for a local address.
It's something that caught a lot of us off-guard...
It's something that caught a lot of us off-guard...
I did that... I have found and install copy of A35 and it works, to have
a FTN address, I upgrade to A39 I cannot put one in where it saves. I
did a fresh install of A39, same thing. I just found a copy of the A35 hanging around and it works fine, I can add a FTN address in.
Is anyone having problems, or is there something I'm over looking??
are you remembering that new mystic versions have to be ""installed"" to a *temp* directory? then you copy over the new binaries, recompile the scripts, and update the default ""language"" file with new additions by overwriting it
like you do with the binaries or if you have modified it you edit yours to fil
in the new prompts/phrasess/words...
it has been a long time since i've updated a mystic setup but you definitely must install the new version to a temp directory and then copy the binaries over and recompile the scripts... that much i definitely remember ;)
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.
On 11-10-18 11:22, mark lewis wrote to Ib Joe <=-
it has been a long time since i've updated a mystic setup but you definitely must install the new version to a temp directory and then
copy the binaries over and recompile the scripts... that much i
definitely remember ;)
On 11/10/18, Ib Joe said the following...
It's something that caught a lot of us off-guard...
I did that... I have found and install copy of A35 and it works, to have a FTN address, I upgrade to A39 I cannot put one in where it saves. I
did a fresh install of A39, same thing. I just found a copy of the A35 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)
* Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)
I'm starting to hate linux... :) I have installed A39 on my Windows 10 32Bit vertual box and, last night, installed it on my Windows 10 64Bit host and I get the same. I enter in my address, or any for the matter,
I fill it out complete ... and it dose not save when I back out.
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 11/10/18, nugax said the following...
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
Nah, turns out he missed the replies that said not to use the first slot, >it's reserved for local mail. =) He figured it out.
--- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
* Origin: http://www.throwbackbbs.com -\- meriden, ct -\- (1:142/799)
it has been a long time since i've updated a mystic setup but you
definitely must install the new version to a temp directory and then
copy the binaries over and recompile the scripts... that much i
definitely remember ;)
The one addition I would make is that if it were a fresh install the install directory must not already exist or the install would fail.
On 11/10/18, Ib Joe said the following...
I'm starting to hate linux... :) I have installed A39 on my Windows 32Bit vertual box and, last night, installed it on my Windows 10 64Bi host and I get the same. I enter in my address, or any for the matte I fill it out complete ... and it dose not save when I back out.
That might be a corrupted data file then. I'm not sure which data file it stores those in. Looks like it might be in the MYSTIC.DAT file, which if it is corrupted, would definitely suck since it keeps a bunch of other stuff in there as well. I'm not sure what you could do.
That might be a corrupted data file then. I'm not sure which data fil stores those in. Looks like it might be in the MYSTIC.DAT file, which it is corrupted, would definitely suck since it keeps a bunch of othe stuff in there as well. I'm not sure what you could do.
Is there a way to fix this file??
Just an update that work is afoot to release a new alpha for Mystic that will address the issue I posted about a week or so ago. This new update when released will also offer significant changes to the way Mystic handles themes along with other tweaks to the code. More to follow when it's out.
This is wonderful news! Looking forward to test out new and shiny .. probably one day one can get BBS online ... Finally!
I have updated to the latest Pre-Alpha... I have never updated any of my prompts... I saw mention of them in the update file... If I have never
in the past updated prompts I can just ignore their mention...??
Sysop: | Weed Hopper |
---|---|
Location: | Clearwater, FL |
Users: | 12 |
Nodes: | 6 (0 / 6) |
Uptime: | 10:56:24 |
Calls: | 115 |
Files: | 50,356 |
D/L today: |
70 files (10,389K bytes) |
Messages: | 298,989 |