On 04-15-20 15:03, Alpha wrote to Vk3jed <=-
From Dan/Black Panther:
----
In order to set up a QWK network within Mystic is not very difficult,
and it does work. Trust me.
Thanks, this is the post I was looking for, though since I've posted, I pretty much worked it out, except that I cheated and did the first stage of setting up the message areas with a dummy .NA file, to get the bulk
On 04-15-20 23:36, Alpha wrote to Vk3jed <=-
Thanks, this is the post I was looking for, though since I've posted, I pretty much worked it out, except that I cheated and did the first stage of setting up the message areas with a dummy .NA file, to get the bulk
Awesome. I feel like this is exactly the kind of stuff that we could collect into a kind of unofficial github repo or wiki for future
reference :)
How about the "The Unofficial Guide to Mystic BBS"
On 04-15-20 21:23, nugax wrote to Vk3jed <=-
I can assist if needed.
I can assist if needed.Thanks :) Looks like I have it working. I did cheat a bit and made
up a dummy .NA file to import, to do the donkey work of setting up
the areas, then went back through them, fixed any errors and added
the QWK networking information to each area by hand.
Anyway, The Bridge is connected to Freeway for DOVE-Net via QWK. :)
.. I distinctly remember forgetting that. === MultiMail/Win v0.51
--- SBBSecho 3.10-Linux * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
On 04-15-20 22:23, nugax wrote to All <=-
I can assist if needed.Thanks :) Looks like I have it working. I did cheat a bit and made
up a dummy .NA file to import, to do the donkey work of setting up
the areas, then went back through them, fixed any errors and added
the QWK networking information to each area by hand.
Awesome!
On 04-15-20 22:23, nugax wrote to All <=-
I can assist if needed.
Thanks :) Looks like I have it working. I did cheat a bit and
made up a dummy .NA file to import, to do the donkey work of
setting up the areas, then went back through them, fixed any
errors and added the QWK networking information to each area by
hand.
Awesome!Hmm, any reason that reply was directed to all? It was obviously
my message. No biggie, just curious. :)
.. 17. Never lie to your doctor. === MultiMail/Win v0.51 ---
SBBSecho 3.10-Linux * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
Does anyone here know how to setup Mystic as a QWK node? I've started
the process, but haven't got it working yet, and the instructions aren't on the wiki wither.
On 04-16-20 10:12, gallaxial wrote to Vk3jed <=-
On 15 Apr 2020, Vk3jed said the following...
Does anyone here know how to setup Mystic as a QWK node? I've started
the process, but haven't got it working yet, and the instructions aren't on the wiki wither.
ok, its not Dificult to do
here i get :
On 04-16-20 06:12, nugax wrote to All <=-
Hmm, any reason that reply was directed to all? It was obviously
my message. No biggie, just curious. :)
I am using a NNTP client and it only allows me to post to all.
.. 17. Never lie to your doctor. === MultiMail/Win v0.51 ---
SBBSecho 3.10-Linux * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
--
Sincerely,
Chad Adams
-- HotdogEd v2.13.5/Android
On 04-16-20 10:12, gallaxial wrote to Vk3jed <=-
On 15 Apr 2020, Vk3jed said the following...
Does anyone here know how to setup Mystic as a QWK node? I've started the process, but haven't got it working yet, and the instructions aren't on the wiki wither.
ok, its not Dificult to do
here i get :
Thanks, managed to work that out just before someone forwarded me Black Panther's post. Only difference from standard procedure that I did was cheat on the donkey work of adding in the area names, etc, by generating a "dovenet.na" file from my Synchronet BBS. That meant all I had to do was enter the QWK networking information (QWK network and conference number) in each area and make minor fixes to the imported data.
On 04-16-20 21:51, Digital Man wrote to Vk3jed <=-
If you import a QWK CONTROL.DAT file instead, then get both the names *and* the conference numbers all in one go. And if you import it via
the SCFG->Networks->QWK->Hubs... Import Conferences menu option, it
does all the hub setup for you as well.
If you import a QWK CONTROL.DAT file instead, then get both the names *and* the conference numbers all in one go. And if you import it via the SCFG->Networks->QWK->Hubs... Import Conferences menu option, it does all the hub setup for you as well.
I don't know if that Mystic has that option.
On 04-16-20 21:51, Digital Man wrote to Vk3jed <=-
If you import a QWK CONTROL.DAT file instead, then get both the names *and* the conference numbers all in one go. And if you import it via the SCFG->Networks->QWK->Hubs... Import Conferences menu option, it does all the hub setup for you as well.
I don't know if that Mystic has that option.
On 04-17-20 15:34, Alpha wrote to Vk3jed <=-
Yeah, I think DM is talking about SBBS's setup--which is quite
automated. Would be awesome if Mystic has the same ability to import
QWK conference numbers as well. I did the same thing--edit the areas
file so I could at least use mutil to import the areas. Then just some manual labor to assign the conference numbers. But it works!
Speaking of making things easier, I don't know if you've seen some of
the stuff DM is working on in terms of puling FTN (Fido + othernets)
info from the internet and automating network setup within the
Synchronet admin, but it's shaping up to be fantastic. I think network setup is something we all struggle with as new Sysops, and to remove
this friction in a modern way would be cool :)
Would be a nice Mystic feature, as well :)
On 04-17-20 12:03, Digital Man wrote to Vk3jed <=-
Re: Re: QWK networking?
By: Vk3jed to Digital Man on Fri Apr 17 2020 09:26 pm
On 04-16-20 21:51, Digital Man wrote to Vk3jed <=-
If you import a QWK CONTROL.DAT file instead, then get both the names *and* the conference numbers all in one go. And if you import it via the SCFG->Networks->QWK->Hubs... Import Conferences menu option, it does all the hub setup for you as well.
I don't know if that Mystic has that option.
Ah, yes. It'd be cool if it did though. :-)
Reminds me, I must export my QWK conferences in a format more suited to QWK improtation and add that to the infopack. :) I'm all for making a sysop's life easier, if I can.
On 04-17-20 23:31, Digital Man wrote to Vk3jed <=-
Re: Re: QWK networking?
By: Vk3jed to Digital Man on Sat Apr 18 2020 11:43 am
Reminds me, I must export my QWK conferences in a format more suited to QWK improtation and add that to the infopack. :) I'm all for making a sysop's life easier, if I can.
For Synchronet, that format would be CONTROL.DAT. :-)
On 04-17-20 23:31, Digital Man wrote to Vk3jed <=-
Re: Re: QWK networking?
By: Vk3jed to Digital Man on Sat Apr 18 2020 11:43 am
Reminds me, I must export my QWK conferences in a format more suited to QWK improtation and add that to the infopack. :) I'm all for making a sysop's life easier, if I can.
For Synchronet, that format would be CONTROL.DAT. :-)
from a QWK packet?
On 04-18-20 04:06, Digital Man wrote to Vk3jed <=-
from a QWK packet?
Correct. That file is normally included in a QWK packet and includes
both the conference names and numbers.
This information is using the most current version of Mystic BBS at the time of this writing, which is 1.12 A 31.
----- ---------------<snip>
First, make sure you have a QWK account set up on the hub BBS. If this is Synchronet, make sure you log in and set the areas you would like, along with the message pointers. Make sure you obtain a list of the conferences and the QWK Base ID numbers, as you will need that information to set up the message bases.
1 - Open Mystic with "mystic -cfg" (or ./mystic -cfg in Linux).
2 - Under Configuration, select "QWK Networking"
3 - If nothing is listed in this menu, select "/" on your keyboard, and chose "Insert"
4 - Hit enter on the newly created network connection
to test a few things with Mystic so here we are. Trying to get DOVE-Net from my system, not VERT.
? ? QWK Base ID ? 2030 Allow ANSI ? No
There's maybe 2 of the messages bases showing with correct messages, the rest aren't in their proper section. I've confirmed the QWK Base ID matches the Synchronet Conference Numbers for all of them as well as the QWK Names.
It's the conference numbers that matter (not the names). Unless you have 30 subs in DOVE-Net *or* you have static QWK conference numbering enabled for those subs, then 2030 is probably incorrect. If you look at the CONTROL.DAT file included in the QWK packet downloaded from the hub, that should inform you what the actual/correct conference numbers should be for that hub.
From Dan/Black Panther:
----
In order to set up a QWK network within Mystic is not very difficult, and it does work. Trust me.
I copied these instructions to http://wiki.synchro.net/howto:dove-net-for-mystic
I copied these instructions to http://wiki.synchro.net/howto:dove-net-for-mysticDo you happen to know if Mystic A47 still has the QWK bug mentioned
within the post above? As I don't really know much about QWK, I was wondering if this is still something I need to be worried about?
Do you happen to know if Mystic A47 still has the QWK bug mentioned
within the post above? As I don't really know much about QWK, I was wondering if this is still something I need to be worried about?
Or better yet, you could just upgrade to A48 and not have to worry if an A47 bug is still around or not, especially since it is most likely
already fixed. ;)
Do you know when A48 will be officially released - A47 is still listed
as the stable version on mysticbbs.com?
The stable releases (actual releases) are often rather far apart,
perhaps 1-2 years. Given that A47 was released last Christmas, I would
say perhaps in a year or so.
But the A47 release was actually very good, so I think you'll be doing rather fine on it. :)
As this particular bug was listed for A31, I was hoping it had long
since been fixed.
Do you know when A48 will be officially released - A47 is still listed
as the stable version on mysticbbs.com?
Yikes. Then I would assume it has long since been fixed. I don't even remember A31 it's been that long ago. ;)
To be completely honest, no. But I've never really thought of Mystic having many "official releases". A47 is/was a prealpha, yet there may
have been some kind of A47 "is as stable as can be" release right before A48 was started. There were MANY versions of A47 leading up to it,
though. This is exactly how A48 has been going. The only reason there isn't a stable version of A48 listed on mysticbbs.com yet is because A49 hasn't been started yet.
I've been upgrading the prealphas as they're released and have had no issues. Sure there may be a few bugs here and there (definitely nothing show-stopping), but g00r00 is on top of it and usually pushes fixes as soon as he is able to.
http://mysticbbs.com/downloads/prealpha
I think the more people that are on the latest version finding bugs and reporting them would be much more helpful to development than people reporting bugs from previous versions. And actually, I'm not sure
previous versions are even supported. The first thing you would be asked to do would be to upgrade to the latest prealpha and see if the
bug/issue is still there, since it may have already been fixed (this is why the whatsnew.txt is important, as well).
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 90 |
Nodes: | 16 (0 / 16) |
Uptime: | 07:54:42 |
Calls: | 5,073 |
Calls today: | 5 |
Files: | 8,491 |
Messages: | 352,797 |