• Hatch

    From Vincent Coen@2:250/1 to All on Tue Jan 18 17:26:18 2022
    Hello All!

    How can I get hatch to accept multiple lines of descriptions for a specific file
    as one liners are not cutting it ?



    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Vincent Coen@2:250/1 to Sean Dennis on Tue Jan 18 20:00:48 2022
    Hello Sean!

    Tuesday January 18 2022 13:02, you wrote to me:

    Hello Vincent,

    Tuesday January 18 2022 17:26, you wrote to All:

    How can I get hatch to accept multiple lines of descriptions for
    a specific file as one liners are not cutting it ?

    Add additional "DESC" lines to the "hatch" script. What I'd do is
    read in the FILE_ID.DIZ and split it into the standard 10 45-char
    lines as per the FILE_ID.DIZ specification.

    The hatch program as near as I can tell does NOT read the FILE_ID.DIZ but accepts a line for the description.

    The code could say :
    x = 0
    while until hatch.desc (1:4) = " " */ chars 1 thru 4 /*
    move spaces (1:4) to hatch.desc
    hatch.desc (x) = input from keyboard
    x + Length of input
    end while

    Routine to copy hatch to new tic file.

    the content of hatch as in file mbselib.h

    --
    /*
    * Hatch manager (hatch.data)
    */
    struct _hatchhdr {
    int hdrsize; /* Size of header */
    int recsize; /* Size of records */
    int lastupd; /* Last stats update */
    };

    struct _hatch {
    char Spec[79]; /* File spec to hatch */
    char Name[21]; /* File Echo name */
    char Replace[15]; /* File to replace */
    char Magic[15]; /* Magic to update */
    char Desc[256]; /* Description for file */
    unsigned DupeCheck : 1; /* Check for dupes */
    unsigned Active : 1; /* Record active */
    unsigned Deleted : 1; /* Record is deleted */
    unsigned short Days[7]; /* Days in the week */
    unsigned short Month[32]; /* Days in the month */
    statcnt Hatched; /* Hatched statistics */
    };
    --

    The original code looks like this :

    --
    for (i = 0; i < strlen(hatch.Desc); i++) {
    if (hatch.Desc[i] != '%') {
    fprintf(Tf, "%c", hatch.Desc[i]);
    } else {
    i++;
    memset(&tmp, 0, sizeof(tmp));
    if (isdigit(hatch.Desc[i]))
    tmp[0] = hatch.Desc[i];
    if (isdigit(hatch.Desc[i+1])) {
    tmp[1] = hatch.Desc[i+1];
    i++;
    }
    fprintf(Tf, "%c", de->d_name[atoi(tmp) -1]);
    }
    }
    --

    And no I do not understand the C code but as the size of desc is 256 chars am right in assuming the accept for that field will take a max length of 256 for the description as in one line but if that is true there is no code to break in
    done into individual lines and the program does not ask for another line let alone doing so wait for a blank line.



    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Alan Ianson@1:153/757 to Sean Dennis on Tue Jan 18 13:11:38 2022
    How can I get hatch to accept multiple lines of descriptions for a
    specific file as one liners are not cutting it ?

    Add additional "DESC" lines to the "hatch" script. What I'd do is read in the FILE_ID.DIZ and split it into the standard 10 45-char lines as per the FILE_ID.DIZ specification.

    There should only be one "Desc" line in a tic file, it doesn't need to be a short one liner, but it should all be on one line.

    There can be multiple "LDesc" lines but that is different.

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Vincent Coen@2:250/1 to Sean Dennis on Tue Jan 18 21:11:00 2022
    Hello Sean!

    Tuesday January 18 2022 13:02, you wrote to me:

    Hello Vincent,

    Tuesday January 18 2022 17:26, you wrote to All:

    How can I get hatch to accept multiple lines of descriptions for
    a specific file as one liners are not cutting it ?

    Add additional "DESC" lines to the "hatch" script. What I'd do is
    read in the FILE_ID.DIZ and split it into the standard 10 45-char
    lines as per the FILE_ID.DIZ specification.

    Just checked but it is not that c module but a script in script called yep, hatch and this is added to the ~/bin directory..

    May well be that the C code is for processing Magic or/and hatch via the menu system.

    Now that I could use but it is designed for regular releases as an archive (with
    a FILE_ID.DIZ) included.

    The script is a one liner only.

    Michael did not make it easy :)

    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From mark lewis@1:3634/12.73 to Sean Dennis on Tue Jan 18 17:02:50 2022

    On 2022 Jan 18 16:27:00, you wrote to Alan Ianson:

    So you can have a single DESC with multiple LDESC lines in a TIC?

    http://ftsc.org/docs/fts-5006.001

    =====>8 snip 8<=====
    Desc

    A one line description of the file to be distributed.

    Example: Desc Region 28 nodelist segment for day 208

    This is an optional keyword


    Ldesc

    This Keyword may occur more than once. If there is more than one
    they should be grouped together. Together they form a long
    description of the file to be distributed.

    Example: Ldesc This is a utility that everyone must have.
    Ldesc It beats all and everything you ever had.

    This is an optional keyword.
    =====>8 snip 8<=====


    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
    ... Men will vacuum when Sears makes one you can ride on.
    ---
    * Origin: (1:3634/12.73)
  • From Alan Ianson@1:153/757 to Sean Dennis on Tue Jan 18 14:01:04 2022
    There should only be one "Desc" line in a tic file, it doesn't need to
    be a short one liner, but it should all be on one line.

    There can be multiple "LDesc" lines but that is different.

    Thank you for that very important clarification.

    So you can have a single DESC with multiple LDESC lines in a TIC?

    Yes, the LDesc lines are usually formatted like a file_id.diz with lines not being more than 45 characters wide.
    --- BBBS/Li6 v4.10 Toy-5
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Sean Dennis@1:18/200 to mark lewis on Tue Jan 18 20:21:00 2022
    mark lewis wrote to Sean Dennis <=-

    http://ftsc.org/docs/fts-5006.001

    Thank you very much for the clarification!

    -- Sean

    ... My other computer is a Coleco ADAM.
    ___ MultiMail/FreeBSD v0.52

    --- Maximus/2 3.01
    * Origin: Outpost BBS (1:18/200)
  • From mark lewis@1:3634/12.73 to Sean Dennis on Wed Jan 19 09:23:48 2022

    On 2022 Jan 18 20:21:00, you wrote to me:

    http://ftsc.org/docs/fts-5006.001

    Thank you very much for the clarification!

    you're quite welcome :)

    )\/(ark

    "The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
    ... The human race is old enough to know better!
    ---
    * Origin: (1:3634/12.73)
  • From Vincent Coen@2:250/1 to Sean Dennis on Wed Jan 19 15:23:58 2022
    Hello Sean!

    Tuesday January 18 2022 16:12, you wrote to me:

    Hello Vincent,

    Tuesday January 18 2022 20:00, you wrote to me:

    The hatch program as near as I can tell does NOT read the
    FILE_ID.DIZ but accepts a line for the description.

    Let me look into this. I should be able to write a bash script to do
    this.

    I have re-discovered a way around it if the files will be hatched more than once by using the FILES hatch facility how ever that also uses a one liner so the file needs to be an archive with FILE_ID.DIZ within.

    This has forced me to issues the files FILEGATE.HDR and FILEGATE.ZXX within there own archives with a .DIZ file.

    OK, but I cannot handle one off's.

    This could be a problem when filegate contributors send me files adhoc via a email or just uploaded into the inbound directory for me to process.

    Clearly it is best (for me at least) for them to connect to a Hub such as here and upload it along with the .tic file but that assumes they have the appropriate software on their system and are running at least a mailer or can use anonymous ftp to get to my server.

    It can get tricky :)

    Clearly using automation is best for them and myself - being a bit of a lazy git :)


    Vincent
    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Sean Dennis@1:18/200 to Vincent Coen on Wed Jan 19 12:20:54 2022
    Hello Vincent,

    Wednesday January 19 2022 15:23, you wrote to me:

    Clearly using automation is best for them and myself - being a bit of
    a lazy git :)

    I wouldn't call it lazy but being more efficient.

    I was looking into things last night but I am surprisingly busy right now. I finally have MBSE running under FreeBSD and am working on switching over to running MBSE again full-time. I have my OS/2 BBS fairly automated and that makes it very easy for me so no reason not to try to build that functionality into MBSE also.

    -- Sean

    ... An engineer is someone who does list processing in Fortran.
    --- GoldED/2 3.0.1
    * Origin: Outpost BBS Sysop Console (1:18/200)
  • From Vincent Coen@2:250/1 to Sean Dennis on Thu Jan 20 01:20:56 2022
    Hello Sean!

    Wednesday January 19 2022 12:20, you wrote to me:

    Hello Vincent,

    Wednesday January 19 2022 15:23, you wrote to me:

    Clearly using automation is best for them and myself - being a
    bit of a lazy git :)

    I wouldn't call it lazy but being more efficient.

    I was looking into things last night but I am surprisingly busy right
    now. I finally have MBSE running under FreeBSD and am working on
    switching over to running MBSE again full-time. I have my OS/2 BBS
    fairly automated and that makes it very easy for me so no reason not
    to try to build that functionality into MBSE also.

    Look forward to it, Thanks Sean.

    I did have a look at the hatch.c code but realised yesterday it is NOT to
    run the independent hatch operation but within the mbsebsb system. A script called hatch is run and I could not work how to change it.



    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Sean Dennis@1:18/200 to Vincent Coen on Thu Jan 20 10:36:38 2022
    Hello Vincent,

    Thursday January 20 2022 01:20, you wrote to me:

    I did have a look at the hatch.c code but realised yesterday it is NOT
    to run the independent hatch operation but within the mbsebsb system.
    A script called hatch is run and I could not work how to change it.

    The "hatch" script itself isn't too bad. I could write a program that could extract FILE_ID.DIZ from an archive and arrange it in both a short DESC line then build LDESC lines from that.

    -- Sean

    ... A drunken man's words are a sober man's thoughts.
    --- GoldED/2 3.0.1
    * Origin: Outpost BBS Sysop Console (1:18/200)
  • From Vincent Coen@2:250/1 to Sean Dennis on Thu Jan 20 19:53:16 2022
    Hello Sean!

    Thursday January 20 2022 10:36, you wrote to me:

    Hello Vincent,

    Thursday January 20 2022 01:20, you wrote to me:

    I did have a look at the hatch.c code but realised yesterday it
    is NOT to run the independent hatch operation but within the
    mbsebsb system. A script called hatch is run and I could not work
    how to change it.

    The "hatch" script itself isn't too bad. I could write a program that
    could extract FILE_ID.DIZ from an archive and arrange it in both a
    short DESC line then build LDESC lines from that.

    That would be great if you can spare the time and with your permission and after testing I would add it to the mbse sources for others to use.

    Funny enough there is NO documentation regarding this hatch script and I really
    tried hard to find any so the current one must have been from a contributor that Micheal never used.

    Thanks for your help.

    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Sean Dennis@1:18/200 to Vincent Coen on Thu Jan 20 19:56:18 2022
    Vincent Coen wrote to Sean Dennis <=-

    That would be great if you can spare the time and with your permission
    and after testing I would add it to the mbse sources for others to use.

    I'd release it under the BSD License so it'd have to be an "add-on" not included with the source. It would be up on my Sourceforge account though.

    Funny enough there is NO documentation regarding this hatch script and
    I really
    tried hard to find any so the current one must have been from a contributor that Micheal never used.

    Michiel himself may have wrote it; it's not a technically complicated script thankfully. I do intend on writing documentation about that script
    eventually.

    -- Sean

    ... Reality is for people who can't face science fiction.
    ___ MultiMail/FreeBSD v0.52

    --- Maximus/2 3.01
    * Origin: Outpost BBS (1:18/200)
  • From Michael Dillon@1:18/200 to Vincent Coen on Wed Jan 26 17:09:00 2022
    The original code looks like this :

    --
    for (i = 0; i < strlen(hatch.Desc); i++) {
    if (hatch.Desc[i] != '%') {
    fprintf(Tf, "%c", hatch.Desc[i]);
    } else {
    i++;
    memset(&tmp, 0, sizeof(tmp));
    if (isdigit(hatch.Desc[i]))
    tmp[0] = hatch.Desc[i];
    if (isdigit(hatch.Desc[i+1])) {
    tmp[1] = hatch.Desc[i+1];
    i++;
    }
    fprintf(Tf, "%c", de->d_name[atoi(tmp) -1]);
    }
    }
    --


    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

    This code actually just translates the Desc line looking for %NN entries, replacing the NN with the character in the file name itself. Otherwise it just copies the next character in the description.
    ... Heisenberg may have slept here.
    ___ MultiMail/Win v0.52

    --- Maximus/2 3.01
    * Origin: Outpost BBS (1:18/200)