Hello everybody!

Please let me explain what happened recently in Micronet:

I initially wanted to renumber the regions in Micronet's nodelist because I wanted to have more room for easy expansion of the nodelist and to give Mike Powell his own region (he is now Region 25).

Due to piss poor planning on my part and the way my BBS software works, things broke and three regions/nets (300, 510, 520) were immediately removed from the nodelist programatically. When that happened, MBSE did not allow the RCs/NCs of those regions/nets to connect to my system.

With my being hospitalized for four days, that created a lag time in responses that could not be met by last Friday.

The three NCs emailed me their modified segments and I manually inserted them into the weekly programmatic nodelist process.

For some reason, my system didn't process everything right the first time but Andrew connected to my BBS server and manually started the update process again. It worked correctly the second time without issues.

I learned several things and I will make sure something like this doesn't happen again. The nodelist will never need the regions renumbered.

When I first created Micronet, I made some technical mistakes setting up the nodelist. Thankfully, my BBS software can be made to work around those issues.

So I apologize for any issues I caused. Thanfully, Micronet appears to be running normally again.

-- Sean

... "When I was a boy the Dead Sea was only sick." - George Burns
--- GoldED+/LNX 1.1.5-b20240209
* Origin: Outpost BBS * Johnson City, TN (618:618/1)

OT, but....

... "When I was a boy the Dead Sea was only sick." - George Burns

...stolen! :D

Mike

* SLMR 2.1a * All Aboard!!!
--- SBBSecho 3.20-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (618:250/1)