This is strange

Win7 Mystic 1.12 A35 32bit

Usually no issue importing the nodelist for fsxNet that I hatch.

File name is compressed by PKZIP 2.04g and is called is FSXNET.Z00

When I try to run the nodelist compile Mystic fails to open it

[snip]

+ Oct 23 16:51:27 Merging fsxnet
+ Oct 23 16:51:27 Searching for "c:\bbs\files\fsx\fsx_node\fsxnet.*"
+ Oct 23 16:51:27 Found "FSXNET.Z00"
+ Oct 23 16:51:27 Searching for "c:\bbs\mystic\temputil\fsxnet.*"
+ Oct 23 16:51:27 Results: Merged 5 of 5 nodelist(s) in 4.59s

[snip]

Then if I rename the extension of the same file to FSXNET.Z93 and re-run the process Mystic will open the compressed file and then import the nodelist.

[snip]

+ Oct 23 16:55:10 Merging fsxnet
+ Oct 23 16:55:10 Extracting FSXNET.Z69
! Oct 23 16:55:10 unzip -oqqjC c:\bbs\files\fsx\fsx_node\FSXNET.Z69 * -d c:\bbs\mystic\temputil\
+ Oct 23 16:55:10 Searching for "c:\bbs\files\fsx\fsx_node\fsxnet.*"
+ Oct 23 16:55:10 Found "FSXNET.Z69"
+ Oct 23 16:55:10 Searching for "c:\bbs\mystic\temputil\fsxnet.*"
+ Oct 23 16:55:10 Found "FSXNET.300"
+ Oct 23 16:55:10 Compare FSXNET.300 2017 / 1980
+ Oct 23 16:55:10 Result 1
+ Oct 23 16:55:10 Merging c:\bbs\mystic\temputil\FSXNET.300

[snip]

Strange huh? It's like the .Z00 extension is not welcome... I did look at it and thought ZOO compression but checked my archivers and there's nothing set.

The file is uncompressed by Mystic using Info-ZIP unzip 6.00

The settings are

Description ³ Info-ZIP Utilities
Pack Cmd ³ zip -qj9 %1 %2
Unpack Cmd ³ unzip -oqqjC %1 %2 -d %3

All of the above config has remained unchanged for ages so it's something in the nature of the extension name I think and the possible combo of an older PKZIP and Info-ZIP unzip.

Thought I'd pass it on, will keep an eye on next weeks nodelist file to see
if this presents issues also.

If anyone else spots this prob with a different distro and/or combo of decompression tools, please let me know :)

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

+ Oct 23 16:55:10 Compare FSXNET.300 2017 / 1980

Looks to me that there is a file date from 1980 possibly?

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 10/23/17, g00r00 pondered and said...

+ Oct 23 16:55:10 Compare FSXNET.300 2017 / 1980

Looks to me that there is a file date from 1980 possibly?

No I think that message reflects (for some reason) the fact that there's only one file to test when it does the checking.

In the case of the fsxNet FSX_NODE file echo and another example for an othernet ... both file bases only ever have one nodelist in them (they are replaced / updated each week by a new file with accompanying TIC that ensure this) so it seems like Mystic assumes a default compare date for the one file present of 1980

[snip]

+ Oct 26 20:23:59 Merging sportnet
+ Oct 26 20:23:59 Extracting SPORTNET.Z93
! Oct 26 20:23:59 unzip -oqqjC c:\bbs\files\sprt\spornode\SPORTNET.Z93 * -d c:\bbs\mystic\temputil\
+ Oct 26 20:23:59 Searching for "c:\bbs\files\sprt\spornode\sportnet.*"
+ Oct 26 20:23:59 Found "SPORTNET.TXT"
+ Oct 26 20:23:59 Found "SPORTNET.Z93"
+ Oct 26 20:23:59 Searching for "c:\bbs\mystic\temputil\sportnet.*"
+ Oct 26 20:23:59 Found "sportnet.293"
+ Oct 26 20:23:59 Compare sportnet.293 2017 / 1980
+ Oct 26 20:23:59 Result 1
+ Oct 26 20:23:59 Merging c:\bbs\mystic\temputil\sportnet.293
+ Oct 26 20:23:59 Merging fsxnet
+ Oct 26 20:23:59 Extracting FSXNET.Z69
! Oct 26 20:23:59 unzip -oqqjC c:\bbs\files\fsx\fsx_node\FSXNET.Z69 * -d c:\bbs\mystic\temputil\
+ Oct 26 20:23:59 Searching for "c:\bbs\files\fsx\fsx_node\fsxnet.*"
+ Oct 26 20:23:59 Found "FSXNET.Z69"
+ Oct 26 20:23:59 Searching for "c:\bbs\mystic\temputil\fsxnet.*"
+ Oct 26 20:23:59 Found "FSXNET.300"
+ Oct 26 20:23:59 Compare FSXNET.300 2017 / 1980
+ Oct 26 20:23:59 Result 1
+ Oct 26 20:23:59 Merging c:\bbs\mystic\temputil\FSXNET.300

[snip]

the above is with the FSXNET.Z00 compressed nodelist renamed to FSXNET.Z69 and successfully importing in to Mystic running 1.12 A36 Pre

If I set the file name back to the correct name of FSXNET.Z00 it still fails
to decompress the file... it's weird.

[snip]

+ Oct 26 20:30:07 Searching for "c:\bbs\mystic\temputil\sportnet.*"
+ Oct 26 20:30:07 Found "sportnet.293"
+ Oct 26 20:30:07 Compare sportnet.293 2017 / 1980
+ Oct 26 20:30:07 Result 1
+ Oct 26 20:30:07 Merging c:\bbs\mystic\temputil\sportnet.293
+ Oct 26 20:30:07 Merging fsxnet
+ Oct 26 20:30:07 Searching for "c:\bbs\files\fsx\fsx_node\fsxnet.*"
+ Oct 26 20:30:07 Found "FSXNET.Z00"
+ Oct 26 20:30:07 Searching for "c:\bbs\mystic\temputil\fsxnet.*"

[snip]

Will keep an eye on it.

Best, Paul

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

If I set the file name back to the correct name of FSXNET.Z00 it still fails to decompress the file... it's weird.

I see what you're saying. I took a look at the code and its true that it only processes the number if it is not zero. I've changed it so it will process 00 also.

I think the number represents the day number which the nodelist was compiled with the first character changed to the compression type. So a valid nodelist would be nodelist.001 through nodelist.365 and a valid ZIPped nodelist would be Z01 through Z99. I think this is why I had it skipping anything that didn't fit that exact format.

Next version will process Z00 through Z99 now.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 10/26/17, g00r00 pondered and said...

Next version will process Z00 through Z99 now.

Thanks :) .. and all good on the other testing, you're most welcome :)

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)