From Mystic logs, I see that the arefix message is reconginized and
appears to process but with obvious issues. The AreaFix Response looks similar to the below logging
Has anyone experieinced something similar?
Hi! Kevin,
On 11/24/2020 05:00 AM, you wrote to All:
From Mystic logs, I see that the arefix message is reconginized and
appears to process but with obvious issues. The AreaFix Response looks
similar to the below logging
[chopped]
Has anyone experieinced something similar?
Yes, with my own Mystic A46. I just thought it was a contamination from my current situation, with Mystic not being the primary receiving agent as it's aligned _behind_ a regular tosser.
I suggest that you persist with the matter in the Mystic echo...
Has anyone experieinced something similar?
From Mystic logs, I see that the arefix message is reconginized and
appears to process but with obvious issues. The AreaFix Response looks
similar to the below logging
[chopped]
Has anyone experieinced something similar?
Yes, with my own Mystic A46. I just thought it was a contamination from my current situation, with Mystic not being the primary receiving agent
as it's aligned _behind_ a regular tosser.
I suggest that you persist with the matter in the Mystic echo...
Hi! Kevin,
On 11/24/2020 05:00 AM, you wrote to All:
From Mystic logs, I see that the arefix message is reconginized and
appears to process but with obvious issues. The AreaFix Response looks
similar to the below logging
[chopped]
Has anyone experieinced something similar?
Yes, with my own Mystic A46. I just thought it was a contamination from my current situation, with Mystic not being the primary receiving agent as it's aligned _behind_ a regular tosser.
Yes, with my own Mystic A46. I just thought it was a contamination
from my current situation, with Mystic not being the primary receiving
agent as it's aligned _behind_ a regular tosser.
Just an FYI... I've been working with g00r00 on this bug which he's just fixed. Will be available in Mystic a48.
Kevin wrote (2020-12-03):
Just an FYI... I've been working with g00r00 on this bug which he's just KM>> fixed. Will be available in Mystic a48.
What triggered the bug? And why did OpenXP trigger it and other software doesn't?
-+-
+ Origin: (2:280/464.47)
Just an FYI... I've been working with g00r00 on this bug which he's
just fixed. Will be available in Mystic a48.
Hi! Kevin,
On 03 Dec 20 08:39, you wrote to me:
Just an FYI... I've been working with g00r00 on this bug which he's
just fixed. Will be available in Mystic a48.
Excellent! I've had a hankering for A47 for the longest time. ;) I
haven't seen the release announcement yet.
g00r00 has actually fixed the bug and compiled it into the a47 pre-alpha.
If you are willing to install a pre-alpha, you can pick it up at the below URL. I updated this morening and confirmed that both areafix and filefix requests are now working again :)
Good luck
Excited to say that OpenXP is again... working as expected!
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 66 |
Nodes: | 4 (0 / 4) |
Uptime: | 15:50:00 |
Calls: | 718 |
Files: | 7,654 |
Messages: | 293,897 |