I would like to thank all of you who replied to me.
look like the world is mine hehehe thank you Paul.

I have downloaded the 2 file FSX_INFO and FSX_NODE and drop them in files
info and node.

do i need to unzip it?
also how do i see a list of user for direct netmail. I tried to type Paul*
amd user not found...?

once again Thank you

Good Day
sysop: Alain Champs
email: alain.champs@champsvisions3d.com

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: Champs Visions 3D (21:2/156)

On 19 May 2019, FoxMolder said the following...

I would like to thank all of you who replied to me.
look like the world is mine hehehe thank you Paul.

I have downloaded the 2 file FSX_INFO and FSX_NODE and drop them in files info and node.

do i need to unzip it?
also how do i see a list of user for direct netmail. I tried to type
Paul* amd user not found...?

once again Thank you

Hey there =)

So your nodelist file from Paul will need to be stored in the folder that
will receive the new nodelists automatically first.

Then once you have done that, you will need to configure your mutil.ini file
to enable Mergenodelists and to configure your fsxNet note in the
Mergenodelist section to point to the zip file with full path, but exluding
the extension. The reason you don't put an extension is that each time a nodelist is hatched it will have a filename of "fsxnet.zXX" where XX is the last 2 digits of the day of the year that the nodelist was created...

So yesterday for example you might have received a nodelist called fsxnet.z39 (for day 139), and that would go into the folder c:\mystic\files\fsx\fsx_node and then you would configure in mutil.ini in the mergenodelist section the folder c:\mystic\files\fsx\fsx_node\fsxnet

Once you have configured this, you can run mutil and pass the mutil.ini as an argument, like this "mutil mutil.ini" and it will run anything that has been enabled within that file, including the mergenodelist section.

Once this has run successfully, in Mystic, in the messaging menu, when you
make a netmail or if you choose the option "B" (default setting) you will be able to query the nodelist that has been merged into Mystic.

If you need a hand with any of this I'm sure there are plenty of people who would be willing to help.

Hope this helps.

By the way, once you're set up with it, I find it useful to split my
mutil.ini up and have individual .ini files for each section I want to use so that I can just call that and run one command rather than a bunch, this is particularly useful for automated events in the events system in Mystic.

Paul has plenty of decent videos on youtube under the guise of The Mystic Guy and I'm pretty sure this is covered in one of them at least =)

Happy BBSing.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)

Happy BBSing.

Oh, I didn't see that you run on a PI, so the paths need to be something like "/mystic/files/fsx/fsx_node/fsxnet" for the nodelist file in the config
instead of what I said like "c:\mystic\files\fsx\fsx_node\fsxnet"

Im sure you'll be ok though, it'll all make some sense in the coming days/weeks/months... soon o.O

have fun, that's the main thing.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)

On 19 May 2019 at 08:07p, MeaTLoTioN pondered and said...

So your nodelist file from Paul will need to be stored in the folder that will receive the new nodelists automatically first.

Thanks for that reply Christian... that's very comprehensive and helpful for
a new user :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 20 May 2019, Avon said the following...

On 19 May 2019 at 08:07p, MeaTLoTioN pondered and said...

So your nodelist file from Paul will need to be stored in the folder will receive the new nodelists automatically first.

Thanks for that reply Christian... that's very comprehensive and helpful for a new user :)

I am just trying to do my bit to pay it forward, I received so much help not too long ago that was invaluable to me, so if I can help out with others now
I know what I'm doing (kinda... sorta... lol) I am happy to lend a helping hand.


While on the subject of nodelists, I have a question about them of my own
that I probably should have asked a long time back but...

I noticed a ways back that every night after importing the new nodelists from FIDO, there were some odd things happening in the nodelist browser if for example I tried to search for 21:1/* where it would have some duplicated
items, some just blank fields and other such oddness.

I figured out a fix, which is basically just after I run the mergenodelist mutil, I will run a script which prunes my newly merged nodelist of all the oddness.

When I first had the odness I looked in the data/nodelist.txt file and found
a ton of entries in random locations that looked something like this;

A345
C732
D914

Each of the above would be randomly placed on a line with a valid node list above and below it... but this would cause some odd behaviour. So my script goes through the data/nodelist.txt file after the merging, and removes these lines. I'm not sure if they do anything other than make a mess of the
nodelist browser in mystic... but here's my script if anyone else has this issue too.


#!/bin/bash

sed '/^[ACD][0-9]*/d' -i /mystic/data/nodelist.txt


That's all it is lol, just one line haha, but it works.

I have no idea if anyone else suffers this, or if it's just me, and if it is, why I am getting this happen every single time a FIDO nodelist comes in, but
it does and it messes up other parts of the file. I think it has to do with
how FIDO sends more than just one file, as they make "amendments" rather than just a whole new nodelist each time, which if it worked would be pretty efficient, however its more of a pain in the rear end than anything else.

Anyway, I'd like to get some feedback on this whether anyone else has this issue and my fix can help them, or if it really is just me lol.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: The Quantum Wormhole, Ramsgate, UK. bbs.erb.pw (21:1/158)

On 20 May 2019 at 06:40a, MeaTLoTioN pondered and said...

I noticed a ways back that every night after importing the new nodelists from FIDO, there were some odd things happening in the nodelist browser
if for example I tried to search for 21:1/* where it would have some duplicated items, some just blank fields and other such oddness.

something is amiss there, can you filebox me a raw nodelist.txt file after
you compile it but before your script runs over it?

Can you also set mergenodelist logging to level 3 and send that log.

Can I also see the stanza you're running in your ini file?

It's curious..

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)