Subj : Re: Hatching Files on Mystic
To   : Mike Dippel
From : Avon
Date : Wed Nov 01 2023 05:05 pm

On 01 Nov 2023 at 04:36p, Avon pondered and said...
 
 Av> On 31 Oct 2023 at 10:31p, Mike Dippel pondered and said...
 Av>  MD> How should the file be written to make it work?
 Av> 
 Av> 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)

.