• CRC Issue

    From Avon@21:1/101 to g00r00 on Fri Dec 28 06:58:28 2018
    HI there

    I'm noticing some issues hatching files. Several that I have downloaded from mysticbbs.com to hatch seem to be failing due to CRC errors when being tossed to nodes. But also I am seeing this in a nodelist generated for fsxNet that also won't toss. I've done nothing at my end so am suspicious of the updated code in A40/41 that may be contributing to this.

    Some examples

    [snip]

    + Dec 28 06:50:40 Process: Toss FDN/TIC Files
    + Dec 28 06:50:40 Tossing FSXNET.Z62.tic
    - Dec 28 06:50:40 Unknown Key (ORIGIN) Value (Origin 21:1/1)
    - Dec 28 06:50:40 Unknown Key (MAGIC) Value (Magic FSX_NODE)
    - Dec 28 06:50:40 Unknown Key (CREATED) Value (Created by ALLFIX,
    6.0.24 Copyright (C) 2000,2013 by Bob Seaborn (1:213/720))
    - Dec 28 06:50:40 Unknown Key (PATH) Value (Path 21:1/1 1545985637 FRI DEC 28 02:15:01 2018 UTC+1200)
    - Dec 28 06:50:40 Unknown Key (SEENBY) Value (Seenby 21:1/1)
    - Dec 28 06:50:40 Unknown Key (SEENBY) Value (Seenby 3:770/1)
    - Dec 28 06:50:40 Unknown Key (SEENBY) Value (Seenby 21:1/2)
    + Dec 28 06:50:40 File FSXNET.Z62 Area FSX_NODE From 21:1/1
    - Dec 28 06:50:40 CRC e6eb14f9 TIC E6EB14F9
    ! Dec 28 06:50:40 Bad file CRC (got e6eb14f9); Moved to c:\mystfsx\files\badfile\
    + Dec 28 06:50:40 Scanning Hatches

    [snip]

    + Dec 28 06:44:22 Tossing 1270fwa2.tic
    - Dec 28 06:44:22 Unknown Key (CREATED) Value (Created by HTick,
    written by Gabriel Plutzar)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc Mystic BBS v1.12 A41
    macOS 64-bit)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc ============================================)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + Free
    feature-crazy multinode BBS software)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + TELNET,RLOGIN,SSH,FTP,NNTP,HTTP,POP/SMTP)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + BINKP/FTP mailer/tosser with Area/FileFix)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + QWK/QWKE
    Networking via FTP transmission)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + Event-based
    menuing system w/ lightbars)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + Powerful language/theme/prompt system)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + Pascal and Python scripting languages)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + JAM message bases w/ QWKE offmail mail)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + Msg editor w/ inline ANSI & spell check)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + Lightbar Sysop-reader-like msg reading)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + Long file names, internal X/Y/Zmodem)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + 99-line file description & FILE_ID.DIZ)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + DOS CP437 and
    UTF8 character translation)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + Many DOS DOOR formats and 32-bit DOOR32)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + Multinode teleconference & user2user chat)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc + BBS list, Voting, Time bank, 1Liners)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc Quote of the day, Rumors, Split Chat,)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc Ansi gallery, top10, fido importers, node)
    - Dec 28 06:44:22 Unknown Key (LDESC) Value (LDesc monitor with full telnet/ssh client, more)
    - Dec 28 06:44:22 Unknown Key (ORIGIN) Value (Origin 21:1/1)
    - Dec 28 06:44:22 Unknown Key (PATH) Value (Path 21:1/1 1545932601 Thu Dec 27 17:43:21 2018 UTC htick/w32-mvcdll 1.9.0-cur 17-08-15)
    - Dec 28 06:44:22 Unknown Key (SEENBY) Value (Seenby 21:1/1)
    - Dec 28 06:44:22 Unknown Key (SEENBY) Value (Seenby 21:1/2)
    + Dec 28 06:44:22 File mys112a41_o64.zip Area FSX_MYST From 21:1/1
    - Dec 28 06:44:22 CRC ee6f6f5e TIC EE6F6F5E
    ! Dec 28 06:44:22 Bad file CRC (got ee6f6f5e); Moved to c:\mystfsx\files\badfile\

    [snip]

    Some of the A41 files hatched just fine, others not.

    Best, Paul


    ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄ Eùavon@bbs.nz ÄÄÄÄÄÄ Wùbbs.nz ÄÄÄ ÄÄÄÄ Kùkeybase.io/avon ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

    --- Mystic BBS v1.12 A41 2018/12/27 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to g00r00 on Fri Dec 28 07:22:12 2018
    On 28 Dec 2018, Avon pondered and said...

    I'm noticing some issues hatching files. Several that I have downloaded from mysticbbs.com to hatch seem to be failing due to CRC errors when being tossed to nodes. But also I am seeing this in a nodelist generated

    Confirming I am unable to hatch

    28/12/2018 07:17 a.m. <DIR> .
    28/12/2018 07:17 a.m. <DIR> ..
    27/12/2018 05:12 p.m. 925,825 mys112a41_l32.rar
    27/12/2018 05:12 p.m. 974,097 mys112a41_l64.rar
    27/12/2018 05:12 p.m. 2,102,128 mys112a41_o64.zip
    27/12/2018 05:12 p.m. 914,622 mys112a41_w32.rar

    all fail with CRC errors.

    I did try to just mass upload them to NET 1 HUB then tested on hatching using Mystic on the l32.rar

    Interesting the same crc value and file size was generated by Mystic as my external tic generator so those bits matched. I then sent the hatched file
    out (including Agency) but saw when it landed at Agency it failed to import
    and presented the same crc error as the reason.

    So either the files are in some way duff or something is off with the code,
    but I now suspect the files as the same crc was calculated using tools like htick and allfix


    ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄ Eùavon@bbs.nz ÄÄÄÄÄÄ Wùbbs.nz ÄÄÄ ÄÄÄÄ Kùkeybase.io/avon ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

    --- Mystic BBS v1.12 A41 2018/12/27 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Black Panther@21:1/186 to Avon on Thu Dec 27 12:01:14 2018
    On 12/28/18, Avon said the following...

    - Dec 28 06:50:40 CRC e6eb14f9 TIC E6EB14F9
    ! Dec 28 06:50:40 Bad file CRC (got e6eb14f9); Moved to

    It looks like it might just be a case issue, as the crc is the same, just uppercase vs lowercase...

    Some of the A41 files hatched just fine, others not.

    What you could do, is hatch the file out with Allfix, then change the .tic
    file 'crc' line to match the case that Mystic is looking for. That would be
    one way to test it.


    ---

    Black Panther(RCS)
    a.k.a. Dan Richter
    Sysop - Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    The sparrows are flying again....

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Avon@21:1/101 to Black Panther on Fri Dec 28 08:11:14 2018
    On 27 Dec 2018, Black Panther pondered and said...

    On 12/28/18, Avon said the following...

    - Dec 28 06:50:40 CRC e6eb14f9 TIC E6EB14F9
    ! Dec 28 06:50:40 Bad file CRC (got e6eb14f9); Moved to

    It looks like it might just be a case issue, as the crc is the same, just uppercase vs lowercase...

    I wondered that also but then when I had Mystic upload the file and generate it's own TIC those files failed to import into Agency and presented with the same CRC error. Mystic and Htick did come up with the same file size and
    CRC... so who knows?


    ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄ Eùavon@bbs.nz ÄÄÄÄÄÄ Wùbbs.nz ÄÄÄ ÄÄÄÄ Kùkeybase.io/avon ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

    --- Mystic BBS v1.12 A41 2018/12/27 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Black Panther@21:1/186 to Avon on Thu Dec 27 12:54:48 2018
    On 12/28/18, Avon said the following...

    - Dec 28 06:50:40 CRC e6eb14f9 TIC E6EB14F9
    ! Dec 28 06:50:40 Bad file CRC (got e6eb14f9); Moved to

    It looks like it might just be a case issue, as the crc is the same, uppercase vs lowercase...

    I wondered that also but then when I had Mystic upload the file and generate it's own TIC those files failed to import into Agency and presented with the same CRC error. Mystic and Htick did come up with the same file size and CRC... so who knows?

    I would have realized that if I'd read the next message... :)

    After disabling the 'Use SSL/TLS' for both hub 1 and for the server, the
    files did transfer, and tossed with no problems. I think I only ended up with the Pi and W64 versions though. I few nodes have already picked them up here
    as well.


    ---

    Black Panther(RCS)
    a.k.a. Dan Richter
    Sysop - Castle Rock BBS
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    The sparrows are flying again....

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Avon@21:1/101 to Black Panther on Fri Dec 28 11:55:46 2018
    On 27 Dec 2018, Black Panther pondered and said...

    After disabling the 'Use SSL/TLS' for both hub 1 and for the server, the files did transfer, and tossed with no problems. I think I only ended up with the Pi and W64 versions though. I few nodes have already picked
    them up here as well.

    Yes I think the ssl/tls stuff may need some more work yet :)


    ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄ Eùavon@bbs.nz ÄÄÄÄÄÄ Wùbbs.nz ÄÄÄ ÄÄÄÄ Kùkeybase.io/avon ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

    --- Mystic BBS v1.12 A41 2018/12/27 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From g00r00@21:1/108 to Avon on Thu Dec 27 19:55:30 2018
    After disabling the 'Use SSL/TLS' for both hub 1 and for the server, files did transfer, and tossed with no problems. I think I only ended with the Pi and W64 versions though. I few nodes have already picked them up here as well.

    Yes I think the ssl/tls stuff may need some more work yet :)

    Just FYI BINKP should have nothing to do with the CRC error. The CRC issue seems related to conversion between 32 and 64-bit integers, not any sort of file transferring.

    --- Mystic BBS v1.12 A42 2018/12/27 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Avon@21:1/101 to g00r00 on Fri Dec 28 14:53:20 2018
    On 27 Dec 2018, g00r00 pondered and said...

    Just FYI BINKP should have nothing to do with the CRC error. The CRC issue seems related to conversion between 32 and 64-bit integers, not
    any sort of file transferring.

    Oh OK, noted, thanks.


    ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄ Eùavon@bbs.nz ÄÄÄÄÄÄ Wùbbs.nz ÄÄÄ ÄÄÄÄ Kùkeybase.io/avon ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

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