Question --

I've been seeing a lot of TIC's from Mystic v1.12 A34 (and perhaps others if I dig deeper) that are missing the 'Origin' member in them.

According to FSP-1039.001 this is a required field. ENiGMA 1/2 currently considers anything without 'Origin' to be an invalid TIC -- it also relies on this field in addition to 'Replaces' to figure out existing items to replace.

Is this a bug or intentional? It's in the spec, but a lot of these specs have/were never really followed to the T anyway, so perhaps I should change the
logic?





--- ENiGMA 1/2 v0.0.6-alpha (linux; x64; 6.10.3)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

On 06/28/17, NuSkooler pondered and said...

Question --

I've been seeing a lot of TIC's from Mystic v1.12 A34 (and perhaps
others if I dig deeper) that are missing the 'Origin' member in them.

According to FSP-1039.001 this is a required field. ENiGMA 1/2 currently considers anything without 'Origin' to be an invalid TIC -- it also
relies on this field in addition to 'Replaces' to figure out existing items to replace.

Is this a bug or intentional? It's in the spec, but a lot of these specs have/were never really followed to the T anyway, so perhaps I should change the logic?

I can say some recent TICs I've sent out in fsxNet were using the recently added hatching code g00r00 is working on. Those had some issues with
incorrect CRC values but that has been fixed now in the upcoming full version of A35

I did a quick test using this newer version and can confirm .TIC files generated by this new alpha doe not include Origin. I'm sure g00r00 can add that in :)

[snip]

Created By Mystic BBS v1.12 A35
Area FSX_INFO
AreaDesc fsx Testing
File fsxinfo.zip
Size 46990
CRC 9fdf64d7
Replaces fsxinfo.zip
Desc ššš ššš
LDesc ššš ššš
LDesc ñøøáøøñ ššøááøêê ñøø øøñ
LDesc ý øøê êøøšêøñššššššøøê êøø net ñ
LDesc êáááá øøê ááá ššš øêø áááýááá ááááê
LDesc ê øø øêêáá øøñ ñøø øêêáêøñ øøø ê
LDesc ý øøøø ñøø øêøø øøñ ñøø øêø øøø ê
LDesc ñ øøøø øáá ñøøššáá øáá ñøê ø ê
LDesc ø øø ááá áá ê
LDesc ø ø fsxnet.txt -- Info & App ê
LDesc ñ ø fsxnet.xxx -- Nodelist ý
LDesc ý fsxnet.zaa -- Nodelist (ZIP) ñ
LDesc ñ ø history.txt -- History ý
LDesc ý systems.txt -- BBS in fsxNet ñ
LDesc ê fsxnet.na -- Echo list ø
LDesc ý fsx_file.na -- File echo list ñ
LDesc ñ £ ý
LDesc ø ££ ššš infopack ê
LDesc ááááááçááááááááááçááááááášñááááááááçáá
Path 21:1/100 Thu Jun 29 19:37:01 2017 UTC Mystic/1.12 A35
Seenby 21:1/100
Seenby 21:1/101
Pw BOGUSPW
To 21:1/101
From 21:1/100

[snip]

I can confirm prior to testing with A34 I have been hatching files using tools that do include the Origin field.

Best, Paul

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

On 06/29/17, Avon said the following...

I've been seeing a lot of TIC's from Mystic v1.12 A34 (and perhaps others if I dig deeper) that are missing the 'Origin' member in them.

I did a quick test using this newer version and can confirm .TIC files generated by this new alpha doe not include Origin. I'm sure g00r00 can add that in :)

I did notice that the other day after receiving some files via Mystic
hatching. I made a temporary fix in MTAFILE to also look for the 'from'
field, as that is what he's using.


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS (RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A34 (Windows/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

According to FSP-1039.001 this is a required field. ENiGMA 1/2 currently considers anything without 'Origin' to be an invalid TIC -- it also

Thanks for the heads up... I took a look into things:

You mentioned many documentation and the FSP. I think FSP are FidoNet proposal documents that anyone can write and propose but aren't part of FidoNet. Actual accepted FidoNet stuff is found in FTS files (FidoNet Technical Standards).
The one I have bookmarked for TIC is:

http://www.filegate.net/ftsc/FTS-5006.001

Anyway, Mystic's hatching is currently broken in A34 it is not putting the "Origin" in and the "Crc" value is wrong. I've fixed both of those things for A35 so your issue should go away. Sorry about that.

I don't think there is anything wrong with your logic keying off of Origin, since the standard documentation does say its a required field (and Mystic will honor that just not in A34 lol whoops)

As a side note, IF Mystic is just tossing a TIC file to downlinks that came from an uplink, it will not add Origin if it is missing (and shouldn't) because that field is supposed to be populated by the system that hatched it.

Thanks again for letting me know. I'll try to toss out A35 soon so you won't have to see those failures coming in.

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

On Thursday, July 6th g00r00 was heard saying...

The one I have bookmarked for TIC is:
http://www.filegate.net/ftsc/FTS-5006.001

Thanks for the response. You are correct about FTS vs FSP/etc.; I've found that
for a lot of this stuff I have to reference both as what is actually in the wild is often a combination or something else entirely :D

I'll keep my code as-is for now then.

Keep up the awesome work on Mystic. It remains one of my main modern inspirations




--- ENiGMA 1/2 v0.0.6-alpha (linux; x64; 6.10.3)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)