I used to use my Wildcat server to hatch my weekly info packets, but I have to do it
using Mystic now.

I have tried doing it by selecting the file, hitting the [H] key to hatch it. I tell it to
replace the old one. Eventually it shows that it did hatch, but my downlinks aren't
getting them apparently.

I see that there is a section of the mutil.ini file for hatching. The 2 files I need to hatch
are HOBBYNET.ZIP and HOBBYNET.XXX (the day the nodelist is hatched.

Do I create a file like hatch.ini (or something like that) to do it, or can I use mutil.ini

How should the file be written to make it work?

Mike Dippel


--- Platinum Xpress/Win/WINServer v7.0
* Origin: The Hobby Line! BBS - hobbylinebbs.com (21:4/176)

On 31 Oct 2023 at 10:31p, Mike Dippel pondered and said...

I used to use my Wildcat server to hatch my weekly info packets, but I have to do it
using Mystic now.

I have tried doing it by selecting the file, hitting the [H] key to
hatch it. I tell it to
replace the old one. Eventually it shows that it did hatch, but my downlinks aren't
getting them apparently.

Mike I'd check the downlinks have a filebox enabled for each of them, without that Mystic won't know where to place the hatched files. Check the downlinks/echonodes are also linked to the file areas you are wanting to send to them. Presume you have set up a TIC password against each echonode also?

For the file boxes you want to set to 'yes' or 'hold' if you want them to poll your HUB for the files.

I see that there is a section of the mutil.ini file for hatching. The 2 files I need to hatch
are HOBBYNET.ZIP and HOBBYNET.XXX (the day the nodelist is hatched.
Do I create a file like hatch.ini (or something like that) to do it, or can I use mutil.ini

Yes you can do that, then you're essentially calling it with MUTIL to get the files hatched via that function.

How should the file be written to make it work?

I'll have a bash at it and post something here in the coming day.

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 01 Nov 2023 at 04:36p, Avon pondered and said...

On 31 Oct 2023 at 10:31p, Mike Dippel pondered and said...

How should the file be written to make it work?

I'll have a bash at it and post something here in the coming day.

Mike there's a couple of ways to call the [AutoHatch] function using MUTIL but I'm going to stick with one way to do that, as you mentioned I'd suggest create a dedicated .ini file for file hatching the stuff you want for your network.

let's call it hatch.ini

In there asides the usual stuff at the top regards logging levels etc. you will want to enable the function

AutoHatch = true

Then you will want to have the function defined.

I'n not sure if the following will work.

[AutoHatch]

; Files will be automatically hatched to connected downlinks
; Each file must already exist in the file base. The format
; file=<base ID or echotag> | filename | replaces filename (optional)

file=10 | HOBBYNET.* | HOBBYNET.*
file=11 | HOBBYNET.ZIP | HOBBYNET.ZIP


The first line assumes your filebase in Mystic for the nodelist is in base ID 10 ... you can change that to your correct one ... now in the case of fsxNet there's only ever one file in there as I use the REPLACE command in the TIC ... what I am unsure about in this example is if the wildcard .* for the extension will work.

It also assumes you have already imported the nodelist file into your Mystic filebase.

For the second line it's a similar story but easier, again set the correct file base ID for the file area you use for your infopack. Because this file retains the same name each time, you can confidently run that line in the ini file, again just make sure your Mystic has a copy of the file you're wanting to hatch out already in it's file base :)

Set your logging to a high level and when you call this function you should see Mystic hatching to each echonodes file boxes... check a filebox and look at the accompanying TIC for the node, check password for that nodes TIC looks OK...

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 11/1/2023 4:23 PM, Avon wrote to Mike Dippel:

On 31 Oct 2023 at 10:31p, Mike Dippel pondered and said...

I used to use my Wildcat server to hatch my weekly info packets, but I have to do it
using Mystic now.

I have tried doing it by selecting the file, hitting the [H] key to hatch it. I tell it to
replace the old one. Eventually it shows that it did hatch, but my downlinks aren't
getting them apparently.

Mike I'd check the downlinks have a filebox enabled for each of them, without
that Mystic won't know where to place the hatched files. Check the downlinks/echonodes are also linked to the file areas you are wanting to send
to them. Presume you have set up a TIC password against each echonode also?

For the file boxes you want to set to 'yes' or 'hold' if you want them to poll
your HUB for the files.

I see that there is a section of the mutil.ini file for hatching. The 2
files I need to hatch
are HOBBYNET.ZIP and HOBBYNET.XXX (the day the nodelist is hatched.
Do I create a file like hatch.ini (or something like that) to do it, or can I use mutil.ini

Yes you can do that, then you're essentially calling it with MUTIL to get the
files hatched via that function.

How should the file be written to make it work?

I'll have a bash at it and post something here in the coming day.

Thanks for getting back to me so quickly.

I assumed that if they are running Mystic, it would automatically create the folder. I
didn't create a .tic file. I didn't have a clue as to how to send the files.

With Wildcat, it would automatically create the .tic file. I just had to specify the folder it
belonged to and it would send that information in the .tic file.

I was hoping that you cold tell me how you hatch your fsxNet files.

Mike Dippel

--- Platinum Xpress/Win/WINServer v7.0
* Origin: The Hobby Line! BBS - hobbylinebbs.com (21:4/176)

On 11/1/2023 4:52 PM, Avon wrote to Mike Dippel:

On 01 Nov 2023 at 04:36p, Avon pondered and said...

On 31 Oct 2023 at 10:31p, Mike Dippel pondered and said...

How should the file be written to make it work?

I'll have a bash at it and post something here in the coming day.

Mike there's a couple of ways to call the [AutoHatch] function using MUTIL but
I'm going to stick with one way to do that, as you mentioned I'd suggest create
a dedicated .ini file for file hatching the stuff you want for your network.

let's call it hatch.ini

In there asides the usual stuff at the top regards logging levels etc. you will
want to enable the function

AutoHatch = true

Then you will want to have the function defined.

I'n not sure if the following will work.

[AutoHatch]

; Files will be automatically hatched to connected downlinks
; Each file must already exist in the file base. The format
; file=<base ID or echotag> | filename | replaces filename (optional)

file=10 | HOBBYNET.* | HOBBYNET.*
file=11 | HOBBYNET.ZIP | HOBBYNET.ZIP

The first line assumes your filebase in Mystic for the nodelist is in base ID
10 ... you can change that to your correct one ... now in the case of fsxNet there's only ever one file in there as I use the REPLACE command in the TIC ...
what I am unsure about in this example is if the wildcard .* for the extension
will work.

It also assumes you have already imported the nodelist file into your Mystic filebase.

For the second line it's a similar story but easier, again set the correct file
base ID for the file area you use for your infopack. Because this file retains
the same name each time, you can confidently run that line in the ini file, again just make sure your Mystic has a copy of the file you're wanting to hatch
out already in it's file base :)

Set your logging to a high level and when you call this function you should see
Mystic hatching to each echonodes file boxes... check a filebox and look at the
accompanying TIC for the node, check password for that nodes TIC looks OK...

You're the best. Will give it a try.

Mike Dippel

--- Platinum Xpress/Win/WINServer v7.0
* Origin: The Hobby Line! BBS - hobbylinebbs.com (21:4/176)

On 31 Oct 2023 at 11:48p, Mike Dippel pondered and said...

Thanks for getting back to me so quickly.

No prob :)

I assumed that if they are running Mystic, it would automatically create the folder. I
didn't create a .tic file. I didn't have a clue as to how to send the files.
With Wildcat, it would automatically create the .tic file. I just had to specify the folder it
belonged to and it would send that information in the .tic file.

Yep when you hatch using Mystic it will generate a TIC file to accompany the file you are wanting to hatch to an echonode.. but you need to have that filebox created and turned on for the echonode and you need to set that echonode to be linked to the filebase in order for it to receive the files you hatch.

I was hoping that you cold tell me how you hatch your fsxNet files.

I'm using a combo of MakeNL to generate the nodelist, batch files and HTick/BinkD to hatch the files and send them to nodes..

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 01 Nov 2023 at 09:06a, Mike Dippel pondered and said...

You're the best. Will give it a try.

Not sure about that, but thanks for the complement.

yep, let me know how you get on and we can suss it together.

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)