• Re: New Area?

    From Al@21:1/110.1 to Vk3jed on Wednesday, September 28, 2016 17:38:00
    Re: Re: New Area?
    By: Vk3jed to Al on Thu Sep 29 2016 08:13 am

    I moved this message to the FSX_MYS area in case you didn't notice.. :)

    1. Format of tic file (I need an overall model, a small number of specific examples just confuses me).

    This is a tic file I recieved here..

    Created by HTick, written by Gabriel Plutzar
    File ech01042.zip
    Area XOFCHUBSLST
    Desc Echos available at 2:5020/1042
    Replaces ech01042.zip
    From 1:123/500
    To 1:153/757
    Origin 2:5020/1042
    Size 14939
    Crc 885548CE
    Path 2:5020/1042 1475096480 Wed Sep 28 21:01:20 2016 UTC htick/w32-mvcdll 1.9.0 -
    Path 2:230/150 1475100027 Wed Sep 28 22:00:27 2016 UTC HTick/lnx 1.4.0-sta 15-0 5
    Path 1:261/38.0 @160928184201 EDT+5
    Path 1:123/500 1475103181 Wed Sep 28 22:53:01 2016 UTC htick/lnx 1.9.0-cur 17-0 8-15
    Seenby 1:16/9999
    Seenby 1:109/500
    Seenby 1:116/18
    Seenby 1:120/640
    Seenby 1:123/500
    Seenby 1:124/5014
    Seenby 1:128/187
    Seenby 1:138/146
    Seenby 1:140/1
    Seenby 1:140/3
    Seenby 1:153/757
    Seenby 1:154/10
    Seenby 1:218/504
    Seenby 1:261/38
    Seenby 1:267/155
    Seenby 1:282/1056
    Seenby 1:320/219
    Seenby 1:322/759
    Seenby 1:340/400
    Seenby 1:342/13
    Seenby 1:393/68
    Seenby 1:2320/100
    Seenby 1:3634/12
    Seenby 2:34/888
    Seenby 2:230/150
    Seenby 2:230/150.1
    Seenby 2:230/152
    Seenby 2:230/152.15
    Seenby 2:280/1027
    Seenby 2:463/1104
    Seenby 2:5010/352
    Seenby 2:5020/113
    Seenby 2:5020/1042
    Seenby 2:5020/1042.3
    Seenby 2:5020/1067
    Seenby 2:5020/1200
    Seenby 2:5020/1853
    Seenby 2:5020/2992
    Seenby 2:5030/87
    Seenby 2:5030/830
    Seenby 2:5030/1474
    Seenby 2:5030/2104
    Seenby 2:5037/7
    Seenby 2:5052/4
    Seenby 2:5053/7
    Seenby 2:5080/68
    Seenby 2:5080/102
    Seenby 2:5083/444
    Seenby 4:90/1
    Seenby 4:801/146
    Seenby 4:801/189
    Pw Secret

    I am going to edit it a bit for an area I'll call VK_INFO, edit as needed..

    File vkradio.zip
    Area VK_INFO
    Desc VKRADIO Net Info Pack.
    Replaces vkradio.zip
    From 1:123/500
    To 1:153/757
    Origin 2:5020/1042
    Size 14939
    Crc 885548CE
    Path 1:123/500 1475103181 Wed Sep 28 22:53:01 2016 UTC htick/lnx 1.9.0-cur Seenby 1:123/500
    Pw Secret

    You'll need to edit the addresses to something that will work with your setup as well as the size of the file will need to be changed. The Crc line is a problem. Mutil will toss a file and tic with an incorrect Crc to the bad file area. When it does that check the log and get the actual Crc for the file and change the Crc line in the tic accordingly and run it through mutil again.

    You could also add a number of LDesc lines with a file description if you needed to do that. Synchronet will use any LDesc lines as the extended description for files that don't contain a file_id.diz

    I think the above will do what you need to send files to your links. You also need to have a filebox setup for nodes you want to send files to since mutil will place outgoing files and tics for those nodes in their fileboxes.

    ... Our program, who art in memory. EXE be thy name.
    --- SBBSecho 3.00-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:1/110.1)
  • From Vk3jed@21:1/109 to Al on Thursday, September 29, 2016 12:17:00
    Al wrote to Vk3jed <=-

    @MSGID: <57EC631E.735.fsx_mys@freeway.apana.org.au>
    @TZ: 41a4
    Re: Re: New Area?
    By: Vk3jed to Al on Thu Sep 29 2016 08:13 am

    I moved this message to the FSX_MYS area in case you didn't notice.. :)

    Yep, makes sense, since I will be using Mystic for this. :)

    1. Format of tic file (I need an overall model, a small number of specific examples just confuses me).

    This is a tic file I recieved here..

    <snip>

    Thanks.



    I am going to edit it a bit for an area I'll call VK_INFO, edit as needed..

    That's the area I will be using :D

    File vkradio.zip
    Area VK_INFO
    Desc VKRADIO Net Info Pack.
    Replaces vkradio.zip
    From 1:123/500
    To 1:153/757
    Origin 2:5020/1042
    Size 14939
    Crc 885548CE
    Path 1:123/500 1475103181 Wed Sep 28 22:53:01 2016 UTC htick/lnx
    1.9.0-cur Seenby 1:123/500
    Pw Secret

    You'll need to edit the addresses to something that will work with your setup as well as the size of the file will need to be changed. The Crc

    Well, already a few sticking points: From, To and Origin are almost magic numbers, because the file is coming from nowhere (manually generated). And why are "from" and "origin" different addresses? I'm assuming "to" would be the FTN address of the hub, since that is the system tossing the file?

    line is a problem. Mutil will toss a file and tic with an incorrect Crc
    to the bad file area. When it does that check the log and get the
    actual Crc for the file and change the Crc line in the tic accordingly
    and run it through mutil again.

    Now that's a pain! Wish there was a standalone utility to calculate the CRC

    You could also add a number of LDesc lines with a file description if
    you needed to do that. Synchronet will use any LDesc lines as the
    extended description for files that don't contain a file_id.diz

    That would be useful, since my infopacks don't have a .doz file in them (yet).

    I think the above will do what you need to send files to your links.
    You also need to have a filebox setup for nodes you want to send files
    to since mutil will place outgoing files and tics for those nodes in
    their fileboxes.

    No probs, that can be sorted.


    ... Yesterday was the deadline for all complaints.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)
  • From Al@21:1/110.1 to Vk3jed on Wednesday, September 28, 2016 19:49:00
    Re: Re: New Area?
    By: Vk3jed to Al on Thu Sep 29 2016 12:17 pm

    I am going to edit it a bit for an area I'll call VK_INFO, edit as
    needed..

    That's the area I will be using :D

    Good guess eh? :)

    Well, already a few sticking points: From, To and Origin are almost magic numbers, because the file is coming from nowhere (manually generated). And why are "from" and "origin" different addresses? I'm assuming "to" would be the FTN address of the hub, since that is the system tossing the file?

    Having never done this I think you will have to experiment. Avon would be a good person to ask about this since he does that in fsxNet.

    Now that's a pain! Wish there was a standalone utility to calculate the CRC

    It is. There is a utility in slackware I was trying to use but it outputs a 9 character crc. There may very well be a utility to calculate the crc so we can add a valid crc in the first place but I'm not sure of what it might be.

    You could also add a number of LDesc lines with a file description
    if you needed to do that. Synchronet will use any LDesc lines as the
    extended description for files that don't contain a file_id.diz

    That would be useful, since my infopacks don't have a .doz file in them (yet).

    Exactly. Please do use LDesc lines. In the end descriptions on the BBS look better.

    ... Not one hundred percent efficient, of course. But nothing ever is.
    --- SBBSecho 3.00-Linux
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:1/110.1)
  • From Avon@21:1/101 to Al on Thursday, September 29, 2016 16:02:00
    On 09/28/16, Al pondered and said...

    Well, already a few sticking points: From, To and Origin are almost m numbers, because the file is coming from nowhere (manually generated) why are "from" and "origin" different addresses? I'm assuming "to" wo be the FTN address of the hub, since that is the system tossing the f

    Having never done this I think you will have to experiment. Avon would
    be a good person to ask about this since he does that in fsxNet.


    I'll be able to help... just need to get home, have dinner and then look into the answers for you guys :)

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From Vk3jed@21:1/109 to Al on Thursday, September 29, 2016 13:11:00
    Al wrote to Vk3jed <=-

    That's the area I will be using :D

    Good guess eh? :)

    Yep. ;)

    Having never done this I think you will have to experiment. Avon would
    be a good person to ask about this since he does that in fsxNet.

    No probs. Just have to find out these details.

    Now that's a pain! Wish there was a standalone utility to calculate the CRC

    It is. There is a utility in slackware I was trying to use but it
    outputs a 9 character crc. There may very well be a utility to
    calculate the crc so we can add a valid crc in the first place but I'm
    not sure of what it might be.

    Have to see if there's something that will work. The 2 pass process will both be a pain and hard to automate, so calculating the CRC externally will make a huge impact.

    You could also add a number of LDesc lines with a file description
    if you needed to do that. Synchronet will use any LDesc lines as the
    extended description for files that don't contain a file_id.diz

    That would be useful, since my infopacks don't have a .doz file in them (yet).

    Exactly. Please do use LDesc lines. In the end descriptions on the BBS look better.

    Yes. :)


    ... Real Programmers Practice Safe HEX
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to Avon on Thursday, September 29, 2016 13:14:00
    Avon wrote to Al <=-

    I'll be able to help... just need to get home, have dinner and then
    look into the answers for you guys :)

    Thanks Paul. :)


    ... When it come to giving, some people stop at nothing.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)
  • From Avon@21:1/101 to Vk3jed on Thursday, September 29, 2016 20:34:00
    On 09/29/16, Vk3jed pondered and said...

    I'll be able to help... just need to get home, have dinner and then look into the answers for you guys :)

    Thanks Paul. :)

    Righto.

    [snip]

    Area AREA_TAG
    Origin 432:1/1
    From 432:1/1
    Replaces VKRADIO.ZIP
    File VKRADIO.ZIP
    Size 32056
    Path 432:1/1 1457209326 SAT MAR 5 14:09:50 2016 UTC+1200
    Seenby 432:1/1
    Pw PASSWORD

    [snip]

    Let's assume you are on Freeway BBS 432:1/102 and you have an echonode set up for 432:1/1 on your system and that echonode has a .TIC password of PASSWORD defined.


    If you place the contents of the example into a .TIC file along with your actual file and toss that into your BBS then Mystic will create .TIC files
    and copys of the file to be sent to other nodes that are connected to that
    file area and place them in their respective fileboxes.

    Note the Replaces line. That's optional but forces Mystic (so long as it's enabled in the file toss stanza) to drop the last version of VKRADIO.ZIP and replace it with your current one.

    The other thing you need to adjust before you run this process is the Size
    line and populate it with the file size (in bytes) of the actual file you are trying to send out. Fail to do this and MUTIL will see it as bad and chuck it into your bad file dir.

    I will work on a video over the next few days to show case all of this.

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From Vk3jed@21:1/109 to Avon on Thursday, September 29, 2016 19:57:00
    Avon wrote to Vk3jed <=-

    @MSGID: <57ECC427.747.fsx_mys@freeway.apana.org.au>
    @TZ: 030c
    On 09/29/16, Vk3jed pondered and said...

    I'll be able to help... just need to get home, have dinner and then look into the answers for you guys :)

    Thanks Paul. :)

    Righto.

    [snip]

    Area AREA_TAG
    Origin 432:1/1
    From 432:1/1
    Replaces VKRADIO.ZIP
    File VKRADIO.ZIP
    Size 32056
    Path 432:1/1 1457209326 SAT MAR 5 14:09:50 2016 UTC+1200
    Seenby 432:1/1
    Pw PASSWORD

    Thanks. Now, what's the "magic number" "1457209326" in the Path line? That one wasn't explained. :)


    ... "Farfrompoopin'" - German word for constipation.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)
  • From Avon@21:1/101 to Vk3jed on Friday, September 30, 2016 12:27:00
    On 09/29/16, Vk3jed pondered and said...

    Path 432:1/1 1457209326 SAT MAR 5 14:09:50 2016 UTC+1200

    Thanks. Now, what's the "magic number" "1457209326" in the Path line? That one wasn't explained. :)

    It's a throwback to a past .tic file I had co-opted. They key thing is that
    you have a Path statement that includes the node sending the file. Beyond the node address the rest of the line is moot and can be ignored.

    How are you getting on?

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From Tony Langdon@21:1/143 to Avon on Thursday, September 29, 2016 23:35:00
    Avon wrote to vk3jed <=-

    On 09/29/16, Vk3jed pondered and said...

    I'll be able to help... just need to get home, have dinner and then look into the answers for you guys :)

    Thanks Paul. :)

    Righto.

    [snip]

    Update: Looks like I can script pretty much all of it, have started work on a "hatch" script, but I'm not quite ready to hatch just yet. So far, my script processes mthe data as follows:

    Area AREA_TAG

    Supplied on command line.

    Origin 432:1/1

    Variable in script $ORIGIN (will consider putting this on the command line for distribution)

    From 432:1/1

    Variable in script $SRC (as above)

    Replaces VKRADIO.ZIP

    From command line, will default to $FILENAME, unless explicitely specified

    File VKRADIO.ZIP

    From command line $FILENAME

    Size 32056

    Determined internally by script.

    Path 432:1/1 1457209326 SAT MAR 5 14:09:50 2016 UTC+1200

    Generated by script using $SRC and a date command with a carefully constructed format string. Still don't know where "1457209326" comes from.

    Seenby 432:1/1

    Using $SRC for this one

    Pw PASSWORD

    I haven't been using TIC passwords, but easily provided in the script
    PASSWORD.

    The other thing you need to adjust before you run this process is the
    Size line and populate it with the file size (in bytes) of the actual

    Turns out that's dead simple in a shell script. :)

    file you are trying to send out. Fail to do this and MUTIL will see it
    as bad and chuck it into your bad file dir.

    I will work on a video over the next few days to show case all of this.

    If I haven't nutted it out by then, I'll check it out. I just have that one "magic number" to resolve.

    The other little question I have is the Fido address of my system. I have both a /1 and /100 AKA at the hub. Echomail normally goes out from /100, just like on FSXnet. What one do you use for your origin and from addresses? I'd have thought the tic would need to come from somewhere else to be processed. ;)

    ... Planet 98% full. Delete politicians? (Y/y)
    ___ MultiMail/Win32 v0.49

    --- Mystic BBS/QWK v1.12 A31 (Raspberry Pi)
    * Origin: The Bridge - bridge.vkradio.com (21:1/143)
  • From Vk3jed@21:1/109 to Avon on Friday, September 30, 2016 09:49:00
    Avon wrote to Vk3jed <=-

    It's a throwback to a past .tic file I had co-opted. They key thing is that you have a Path statement that includes the node sending the file. Beyond the node address the rest of the line is moot and can be
    ignored.

    How are you getting on?

    Well, if I can ignore the magic number, I think I have a script ready for alpha testing. I've managed to programatically generate all of the fields necessary to generate the example .tic, including examining the file to determine its size. :-)


    ... Daddy, why doesn't this magnet pick up your diskettes?
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)
  • From Avon@21:1/101 to Tony Langdon on Friday, September 30, 2016 13:14:00
    constructed format string. Still don't know where "1457209326" comes from.

    Ignore it.

    The other little question I have is the Fido address of my system. I
    have both a /1 and /100 AKA at the hub. Echomail normally goes out from /100, just like on FSXnet. What one do you use for your origin and from addresses? I'd have thought the tic would need to come from somewhere else to be processed. ;)

    It can come from any node number you choose to give it. In my case it's like 21:1/1 from memory.

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From Avon@21:1/101 to Vk3jed on Friday, September 30, 2016 13:15:00

    On 09/30/16, Vk3jed pondered and said...

    Well, if I can ignore the magic number, I think I have a script ready
    for alpha testing. I've managed to programatically generate all of the fields necessary to generate the example .tic, including examining the file to determine its size. :-)

    Very flash, and yes you can. :)

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From Vk3jed@21:1/109 to Avon on Friday, September 30, 2016 10:32:00
    Avon wrote to Tony Langdon <=-

    It can come from any node number you choose to give it. In my case it's like 21:1/1 from memory.

    No probs, well, here goes the smoke test. :-)


    ... Cats make keen alarm clocks. At no extra charge.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to Avon on Friday, September 30, 2016 10:34:00
    Avon wrote to Vk3jed <=-

    Very flash, and yes you can. :)

    I have an almost ADHD side to my nature that makes me very averse to fiddly work (and is often in conflict with my persistent side!), so scrit it is. :D


    ... Just my opinion (but I'm right!).
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)