I just updated the prealphas with some touch ups and one major thing that I
was hesitant to do.

I rewrote the FLO file handling which should make it much more reliable with file locking, I hope. It seems to in Windows at least. But since that is a sort of big change I made a backup of the last pre-alpha released before I did the FLO change. If anyone seems to have issues with it then it will be there to easily roll back to.

http://www.mysticbbs.com/downloads/prealpha/ http://www.mysticbbs.com/downloads/prealpha/previous/

The previous directory has the old FLO system and the normal prealpha has the newer one.

--- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
* Origin: Sector 7 (21:1/108)

I just updated the prealphas with some touch ups and one major thing
that I was hesitant to do.

Just in case anyone downloaded them in the like 10 or 15 minutes after this announcement: I accidentally put the wrong files up but I've since fixed it.

--- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 29 Jan 2020 at 01:55a, g00r00 pondered and said...

I just updated the prealphas with some touch ups and one major thing
that I was hesitant to do.

I rewrote the FLO file handling which should make it much more reliable with file locking, I hope. It seems to in Windows at least. But since that is a sort of big change I made a backup of the last pre-alpha released before I did the FLO change. If anyone seems to have issues
with it then it will be there to easily roll back to.

I never got a chance to grab those old FLO builds you created as when I went
to pull it down the dir was gone :)

So shall I just use this build to update NET 1 with and we see if it flys?

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

On 29 Jan 2020 at 02:35a, g00r00 pondered and said...

Just in case anyone downloaded them in the like 10 or 15 minutes after this announcement: I accidentally put the wrong files up but I've since fixed it.

I'm still trying to add new nodes before bed time arrives *and* squeeze in a HUB update too.. need more hours in the day :)

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

Trying to connect to a node that is having probs after a rebuild.

I get this error

Jan 29 20:23:51 FIDOPOLL Version 1.12 A44 2020/01/28
Jan 29 20:23:51 Looking up address "21:1/135" in nodelist
Jan 29 20:23:51 Scanning 21:1/135
Jan 29 20:23:51 Queued 0 files (0 bytes) to 21:1/135
Jan 29 20:23:51 Polling BINKP node 21:1/135 (Kevin Taylor) by IPV4
Jan 29 20:23:51 Connecting to defshard.synology.me
Jan 29 20:23:52 Using address 73.20.9.87
Jan 29 20:23:52 Connected IPV4 to 73.20.9.87
Jan 29 20:23:52 Auth State:SendWelcome Have:False Need:True
Jan 29 20:23:52 S: NUL SYS fsxHUB Risa [NET1]
Jan 29 20:23:52 S: NUL ZYZ Avon
Jan 29 20:23:52 S: NUL TIME Wed, 29 Jan 2020 20:23:52 +1300
Jan 29 20:23:52 S: NUL VER Mystic/1.12A44 binkp/1.0
Jan 29 20:23:52 S: NUL BUILD 2020/01/28 00:38:25 Windows/32
Jan 29 20:23:52 S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
Jan 29 20:23:52 Auth State:WaitServerAddress Have:False Need:True
Jan 29 20:23:53 New frame detected
Jan 29 20:23:53 Begin receive data frame (Size=16972)
Jan 29 20:23:53 Error receiving data (Msg= Size=7/16972)
Jan 29 20:23:53 Connection lost
Jan 29 20:23:53 Authorization failed

I also see this with a couple of other nodes (one of which is Gryphon) so I
am wondering if it may be a case of IP blocking causing the session to drop
at the node end?

[snip]

Jan 29 20:55:22 Scanning 21:1/120
Jan 29 20:55:22 Queued 15 files (1911833 bytes) to 21:1/120
Jan 29 20:55:22 Polling BINKP node 21:1/120 (Darryl Perry) by IPV4
Jan 29 20:55:22 Connecting to cyberiabbs.zapto.org
Jan 29 20:55:22 Using address 54.193.66.229
Jan 29 20:55:22 Connected IPV4 to 54.193.66.229
Jan 29 20:55:22 Auth State:SendWelcome Have:False Need:True
Jan 29 20:55:22 S: NUL SYS fsxHUB Risa [NET1]
Jan 29 20:55:22 S: NUL ZYZ Avon
Jan 29 20:55:22 S: NUL TIME Wed, 29 Jan 2020 20:55:22 +1300
Jan 29 20:55:22 S: NUL VER Mystic/1.12A44 binkp/1.0
Jan 29 20:55:22 S: NUL BUILD 2020/01/28 00:38:25 Windows/32
Jan 29 20:55:22 S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
Jan 29 20:55:22 Auth State:WaitServerAddress Have:False Need:True
Jan 29 20:55:22 New frame detected
Jan 29 20:55:22 Begin receive data frame (Size=22624)
Jan 29 20:55:22 Error receiving data (Msg= Size=0/22624)
Jan 29 20:55:22 Connection lost
Jan 29 20:55:22 Authorization failed

[snip]

Jan 29 20:55:43 Scanning 21:1/147
Jan 29 20:55:43 Queued 31 files (5428008 bytes) to 21:1/147
Jan 29 20:55:43 Polling BINKP node 21:1/147 (Danny Moss) by IPV4
Jan 29 20:55:43 Connecting to tcnbbs.fsxnet.nz
Jan 29 20:55:43 Using address 203.38.121.134
Jan 29 20:55:43 Connected IPV4 to 203.38.121.134
Jan 29 20:55:43 Auth State:SendWelcome Have:False Need:True
Jan 29 20:55:43 S: NUL SYS fsxHUB Risa [NET1]
Jan 29 20:55:43 S: NUL ZYZ Avon
Jan 29 20:55:43 S: NUL TIME Wed, 29 Jan 2020 20:55:43 +1300
Jan 29 20:55:43 S: NUL VER Mystic/1.12A44 binkp/1.0
Jan 29 20:55:43 S: NUL BUILD 2020/01/28 00:38:25 Windows/32
Jan 29 20:55:43 S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
Jan 29 20:55:43 New frame detected
Jan 29 20:55:43 Begin receive data frame (Size=0)
Jan 29 20:55:43 Auth State:WaitServerAddress Have:True Need:False
Jan 29 20:56:13 Session timeout
Jan 29 20:56:13 Authorization failed

[snip]

Jan 29 20:56:13 Queued 78 files (6615849 bytes) to 21:1/171
Jan 29 20:56:13 Polling BINKP node 21:1/171 (Andreas Selstam) by IPV4
Jan 29 20:56:13 Connecting to modematider.selstam.nu
Jan 29 20:56:14 Using address 46.59.99.51
Jan 29 20:56:14 Connected IPV4 to 46.59.99.51
Jan 29 20:56:14 Auth State:SendWelcome Have:False Need:True
Jan 29 20:56:14 S: NUL SYS fsxHUB Risa [NET1]
Jan 29 20:56:14 S: NUL ZYZ Avon
Jan 29 20:56:14 S: NUL TIME Wed, 29 Jan 2020 20:56:14 +1300
Jan 29 20:56:14 S: NUL VER Mystic/1.12A44 binkp/1.0
Jan 29 20:56:14 S: NUL BUILD 2020/01/28 00:38:25 Windows/32
Jan 29 20:56:14 S: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
Jan 29 20:56:14 Auth State:WaitServerAddress Have:False Need:True
Jan 29 20:56:14 New frame detected
Jan 29 20:56:14 Begin receive data frame (Size=16972)
Jan 29 20:56:14 Error receiving data (Msg= Size=7/16972)
Jan 29 20:56:14 Connection lost
Jan 29 20:56:14 Authorization failed

[snip]

These polls were done using a recent (last 24 hours) version of the A44 Fidopoll - FIDOPOLL Version 1.12 A44 2020/01/28

Best, Paul

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

On 29 Jan 2020 at 01:55a, g00r00 pondered and said...

I rewrote the FLO file handling which should make it much more reliable with file locking, I hope. It seems to in Windows at least. But since that is a sort of big change I made a backup of the last pre-alpha released before I did the FLO change. If anyone seems to have issues
with it then it will be there to easily roll back to.

I updated NET 1 to the latest build.

Could you add in the extra detail that was only just added in more recent logging in mis.txt for me again? It seems to have gone again.. thank you :)

current build

- Jan 29 21:41:07 EXEC: zip -qj9 "c:\mystfsx\echomail\out\fidonet\0000ffa9.weq" "c:\mystfsx\temputil\11c02aab.pkt"
- Jan 29 21:41:07 EXEC: zip -qj9 "c:\mystfsx\echomail\out\fidonet\0000ffa8.weq" "c:\mystfsx\temputil\11c02aab.pkt"
- Jan 29 21:41:07 EXEC: zip -qj9 "c:\mystfsx\echomail\out\fidonet\0000ffa7.weu" "c:\mystfsx\temputil\11c02aab.pkt"

old build

+ Jan 29 00:11:14 Packet already in FLO
- Jan 29 00:11:14 EXEC: zip -qj9 "c:\mystfsx\echomail\out\fidonet\0000ffd4.we0" "c:\mystfsx\temputil\114a1345.pkt"
+ Jan 29 00:11:14 Adding PKT to FLO (addr=21:1/144 pkt=c:\mystfsx\echomail\out\fidonet\0000ffd4.we0 flo=c:\mystfsx\echomail\out\fidonet\00010090.hlo)
+ Jan 29 00:11:14 Packet already in FLO

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

I never got a chance to grab those old FLO builds you created as when I went to pull it down the dir was gone :)

So shall I just use this build to update NET 1 with and we see if it
flys?

I think so. I have the flo.txt logging enabled in the latest build too.

--- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
* Origin: Sector 7 (21:1/108)

Could you add in the extra detail that was only just added in more recent logging in mis.txt for me again? It seems to have gone again.. thank you :)

Its in flo.txt now, but I can add it back to the main log too.

--- Mystic BBS v1.12 A44 2020/01/29 (Linux/64)
* Origin: Sector 7 (21:1/108)

On 29 Jan 2020 at 11:25a, g00r00 pondered and said...

Its in flo.txt now, but I can add it back to the main log too.

Thanks :)

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