Hi Guys,

I'm currently following Mystic Guy's YouTube tutorial for setting up fsxNet nessages, and everything seems to work except I don't seem to have any
messages that are more than a few days old.

Can someone please confirm if this is correct; has fsxnet purged older
messages recently?

Cheers.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: TALIADON BBS (21:1/999)

On 02/26/2021 9:41 pm TALIADON said...

I'm currently following Mystic Guy's YouTube tutorial for setting up fsxNet nessages, and everything seems to work except I don't seem to have any messages that are more than a few days old.

Hey there and welcome!

This is because of your address... 21:1/999 is used for testing. You should contact Avon for one for your system.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: TALIADON BBS (21:1/999)

Take Care,
Beanzilla

--- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.19.0)
* Origin: BZ&BZ BBS (21:4/110)

*** Quoting TALIADON from a message to All ***

Hi Guys,

I'm currently following Mystic Guy's YouTube tutorial for setting up fsxNet nessages, and everything seems to work except I don't seem to
have any messages thatare more than a few days old.

Can someone please confirm if this is correct; has fsxnet purged
older messages recently?

Hi Taliadon & welcome!

It looks like you have everything setup correctly.

-!- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: TALIADON BBS (21:1/999)

^^^^^^^^

If you haven't already, you'll need to send in an application for your own node number. Once you have that, you'll be able to send a netmail message
to Areafix where you can %RESCAN past messages.

Messages you get from the test node number of /999 will only be current are could be shared with others who are also using the same node number.

You can download the infopack which contains the application from here: http://bbs.nz/fsxnet.zip


Note that Paul a.k.a Avon is away at the moment visiting family, so you may not get a reply right away.

Jay

... WARNING! Removal of this tagline prohibited by law!

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms (21:3/110.1)

If you haven't already, you'll need to send in an application for your
own node number. Once you have that, you'll be able to send a netmail message to Areafix where you can %RESCAN past messages.

Messages you get from the test node number of /999 will only be current are could be shared with others who are also using the same node number.

You can download the infopack which contains the application from here: http://bbs.nz/fsxnet.zip

Note that Paul a.k.a Avon is away at the moment visiting family, so you may not get a reply right away.

Jay

Awesome, cheers Jay, your help is very much appreciated.

Lee.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: TALIADON BBS (21:1/999)

This is because of your address... 21:1/999 is used for testing. You should contact Avon for one for your system.

Cheers Beanzilla, your help is very much appreciated.

Lee.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: TALIADON BBS (21:1/999)

as has been said it is due to using the testing node no.

As soon as I got my node number and set it up a couple of hundred messages appeared.

You can also move the pointer back to go back in history and pull back more messages ... watch the Mystic Guy's video called "Area Fix and File Fix Explained + Howto" which will show you how to push the pointer back and download echomail and files prior to your setup

https://www.youtube.com/watch?v=ltNEjNs8hBs

Avon's videos are fantastic

I was choosing between Mystic and Synchronet as a BBS system and found them similarly matched in features. (I think they are virtually matched in
features and was about to choose Synchronet over Mystic because of their support for HTTPS but then found Avon's videos .... the videos on synchronet are few and far between and Avon made it look so easy setting it up I had
mine running in no time on an old Raspberry Pi 3 (Planning on migrating it
to an intel machine shortly to make doors setup easier).

--- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
* Origin: Tribe BBS (21:1/177)

*** Quoting hal from a message to TALIADON ***

Raspberry Pi 3 (Planning onmigrating it to an intel machine shortly
to make doors setup easier).

If you haven't looked at either BBSLink (bbslink.net) or Door Party (wiki.throwbackbbs.com/doku.php) you may want to. This lets you setup doors on your Pi via a remote server, the benefits being that you get to play door games with other users while on your own BBS.

Jay

... Don't drink and park; accidents cause people.

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms (21:3/110.1)

as has been said it is due to using the testing node no.

As soon as I got my node number and set it up a couple of hundred
messages appeared.

You can also move the pointer back to go back in history and pull back more messages ... watch the Mystic Guy's video called "Area Fix and File Fix Explained + Howto" which will show you how to push the pointer back and download echomail and files prior to your setup

https://www.youtube.com/watch?v=ltNEjNs8hBs

Avon's videos are fantastic

I was choosing between Mystic and Synchronet as a BBS system and found them similarly matched in features. (I think they are virtually matched
in features and was about to choose Synchronet over Mystic because of their support for HTTPS but then found Avon's videos .... the videos on synchronet are few and far between and Avon made it look so easy setting it up I had mine running in no time on an old Raspberry Pi 3 (Planning
on migrating it to an intel machine shortly to make doors setup easier).

Cheers Hal.

You're right, the YouTube videos are fantastic.

I've now got my node number and everything appears to be working as it should :)

Next stop is the spellchecker: my spelling is attrosious (see what I mean!)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: TALIADON BBS (21:3/138)

I'm currently working on getting netmail and files to work .... I think I've done something wrong so I'm going to have to go through the videos again and hit the wiki

--- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
* Origin: Tribe BBS (21:1/177)

I'm currently working on getting netmail and files to work .... I think I've done something wrong so I'm going to have to go through the videos again and hit the wiki

I kinda took the easier root and went with Windows as opposed to linux/pi; I had a linux x64 setup for a while, but Mystic would often wind up in an infinite loop (100% cpu) every now and again. The current Win32 version
doesn't seem to have that problem, and doors are easier to get going too :)

I also had trouble with the fsxNet file set-up, but Deon George (NET 3
SYSOP) put me right and things seem to be working as expected (my PKT
password wasn't set up correctly). One thing I did notice is that once you're system has processed the files once (good or bad), it won't automatically
send them again once you've corrected your config (I had to use the "Filefix" interface in order to "RESEND" the files again). I assume they would be automatically sent (rehatched?) again at some point, but I needed to get some files in order to test my config.

Same thing with messages: once I became an fsxNet member and updated my node id, I had to use the "Areafix" interface in order to "RESCAN" the message bases.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: TALIADON BBS (21:3/138)

I kinda took the easier root and went with Windows as opposed to
linux/pi; I
had a linux x64 setup for a while, but Mystic would often wind up in
an
infinite loop (100% cpu) every now and again. The current Win32
version
doesn't seem to have that problem, and doors are easier to get going
too :)

I seem to remember having this exact problem back when I ran Mystic.
Pretty sure it was one of the reasons I moved away from it. I assumed it
was something I was doing wrong. Things would start to get sluggish and
I'd open htop and see mis had maxed out the CPU. Don't remember if anyone
else was having that problem as well...

Cheers,


|03[] |12Alpha
|02TheDrunkenGamer.com|06:|108888
|08A Talisman BBS


--- Talisman v0.10-dev (Linux/x86_64)
* Origin: The Drunken Gamer BBS (21:4/158)

I seem to remember having this exact problem back when I ran Mystic. Pretty sure it was one of the reasons I moved away from it. I assumed it was something I was doing wrong. Things would start to get sluggish and I'd open htop and see mis had maxed out the CPU. Don't remember if anyone else was having that problem as well...

Yeah, that's exactly it; it would often happen when the client closed the session without logging out or when a door was terminating.

Are you running it on a pi at the moment?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: TALIADON BBS (21:3/138)

Are you running it on a pi at the moment?

I'm not running Mystic any longer, but when I did, I remember having the
same problem on a P4 and on Ubuntu 18.04...


|03[] |12Alpha
|02TheDrunkenGamer.com|06:|108888
|08A Talisman BBS


--- Talisman v0.10-dev (Linux/x86_64)
* Origin: The Drunken Gamer BBS (21:4/158)