Mystic BBS v1.12 A44 has been released!
You can download it at www.mysticbbs.com
You can download it at www.mysticbbs.com
I will hatch all copies out now to FSX_MYS file echo also.
Mystic BBS v1.12 A44 has been released!
Thanks. Hopefully it will be a smooth release. I don't think many
people were using the later builds of the prealphas.
I am excited to get to A45 if this goes smoothly.
Thanks. Hopefully it will be a smooth release. I don't think many
people were using the later builds of the prealphas.
On 02-05-20 11:48, g00r00 wrote to Avon <=-
Thanks. Hopefully it will be a smooth release. I don't think many
people were using the later builds of the prealphas.
I am excited to get to A45 if this goes smoothly.
On 02-06-20 09:49, Avon wrote to g00r00 <=-
On 05 Feb 2020 at 11:48a, g00r00 pondered and said...
Thanks. Hopefully it will be a smooth release. I don't think many
people were using the later builds of the prealphas.
Biggest issue I see so far will be understanding where MPLC went :)
following bases FSX_MAG, FSX_HAM (but just spotted two messages with corruption in them, humm) FSX_ENG, and FSX_DAT also seem fine for order
Congrats and thanks for releasing this version :)
Thanks. Hopefully it will be a smooth release. I don't think many people were using the later builds of the prealphas.
I updated most days. Last one prior to this that I used was from 2/2 I think. No problems so far.
following bases FSX_MAG, FSX_HAM (but just spotted two messages with corruption in them, humm) FSX_ENG, and FSX_DAT also seem fine for ord
The corrupted messages are a red herring. I found them also in the 1/100 base so have removed them... so they did export (albeit as corrupted) correctly.
I'm still trying to figure out why some bases when I rinse and repeat a fresh rescan are importing in non chronological order.
Will keep playing.
Congrats and thanks for releasing this version :)
Agreed thanks for all your work on Mystic!
What are you max packet settings for size? If I understood correctly you're doing a huge 150,000 message rescan. I am wondering if its
filling up packets and then running out of "extensions" to use for new packets so messages sort of get "wrapped" into other existing packets. I'll think through this more once I can apply your settings into the logic.
Yes I am sending 1/100 a %rescan d=9999 areafix to it and getting back 36 compressed files with a ton of packets in them. I kept a copy of them so
Yes I am sending 1/100 a %rescan d=9999 areafix to it and getting bac compressed files with a ton of packets in them. I kept a copy of them
This sort of points to maybe what I was saying before then. There are only 36 possible bundles so what happens if you rescan so many messages that all 36 bundles are used and at your maximums. I think at that
point things may be hit or miss as to where they end up when they are exported.
Packets within a bundle are sorted and processed in date/time order but
if there are packets that are spread out within many bundles, those obviously are not - because bundles are processed only one at a time.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 97 |
Nodes: | 16 (0 / 16) |
Uptime: | 03:23:35 |
Calls: | 4,444 |
Calls today: | 5 |
Files: | 8,486 |
Messages: | 348,851 |