Hi Tony,

The best way to do it is to create a dummy tic that you include in your echomail/in folder along with the file that you want to hatch out.

Now the format of this I will post when I get home tonight and you might like to compare and contrast it with what Al will also discuss (here hopefully) to pick up some (if any) differences.

Then you run your MUTIL like any other file import session and ensure you
have other echonodes attached to the file area the .TIC is pointing at and that you have fileboxes set up for each echonode - all before you run MUTIL.

Key things to get right are file area tag, file size, check to see if you using a replace verb or not etc.

I'm at work (lunchtime) but will aim to reply further later.

** Important - please note **

Under the current way that Mystic is built, I think that if you were to hatch a file to an existing fsxNet file base on your BBS, and that filebase was
also attached to the 21:1/100 echonode.. then your system would send a copy of the file to the HUB with an accompanying .TIC, and that the HUB would in turn then send the file and fresh .TICs on to other nodes also connected to that file base.

That's something I'm not sure I'm that comfortable about happening as I wish to remain in control of files being hatched to the fsxNet file bases and also ensure reporting of what has been sent out to nodes etc.

I think the plan was/is for g00r00 sometime in the future to enable hatching features in Mystic file bases based on ACS access. But I am unsure how that would work (as it's not enabled yet) and I am equally unsure how in the case
of a HUB setup running Mystic, that it would avoid the scenario I mentioned above.

So in sum, I'll do my best to help you (and others reading) with this subject but I'll need your co-operation / help also.

Best, Paul

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

Avon wrote to vk3jed <=-

The best way to do it is to create a dummy tic that you include in your echomail/in folder along with the file that you want to hatch out.

Yep, the basic idea makes sense, the devil is in the detail for me.

Now the format of this I will post when I get home tonight and you
might like to compare and contrast it with what Al will also discuss
(here hopefully) to pick up some (if any) differences.

Thanks. It's those details that I got hung up on.

Then you run your MUTIL like any other file import session and ensure
you have other echonodes attached to the file area the .TIC is pointing
at and that you have fileboxes set up for each echonode - all before
you run MUTIL.

Well, the filebases are definitely setup. Have to check which nodes are connected.

Key things to get right are file area tag, file size, check to see if
you using a replace verb or not etc.

Yep, just need those details. Now if I can programatically get the file size in a script. I'm hoping to (semi) automate it using a shell script, so I just have to enter the variable data and point it to the file, and the script does the rest.

I'm at work (lunchtime) but will aim to reply further later.

** Important - please note **

Under the current way that Mystic is built, I think that if you were to hatch a file to an existing fsxNet file base on your BBS, and that filebase was also attached to the 21:1/100 echonode.. then your system would send a copy of the file to the HUB with an accompanying .TIC, and that the HUB would in turn then send the file and fresh .TICs on to
other nodes also connected to that file base.

That's something I'm not sure I'm that comfortable about happening as I wish to remain in control of files being hatched to the fsxNet file
bases and also ensure reporting of what has been sent out to nodes etc.

I'm wanting this for my own file echoes, not any other network. I have 3 file echoes on VKRadio, though at this stage, only my "info" echo, which carries nodelists and infopacks to my connected nodes. In any case, I agree with you and don't want to mess up FSX. All this is for my own net, so I can distribute infopacks to my downlinks from my hub.

I think the plan was/is for g00r00 sometime in the future to enable hatching features in Mystic file bases based on ACS access. But I am unsure how that would work (as it's not enabled yet) and I am equally unsure how in the case of a HUB setup running Mystic, that it would
avoid the scenario I mentioned above.

So in sum, I'll do my best to help you (and others reading) with this subject but I'll need your co-operation / help also.

No dramas, only way you'll see my hatched files is if you join VKRadio *hint* *hint* ;)

BTW, I'd also be interested in what you're using for the announcements. I know it was discussed. Or if there's a way I can generate an echomail post from a text file using a shell script.
... The greatest enemy of creatitivy is staying inside your comfort zone
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)