1. Forum
  2. FidoNet
  3. FE HELP

  • test

    From Tommi Koivula@2:221/1.254 to Martin Kazmaier on Saturday, October 28, 2023 09:56:38
    * Originally in FIDOTEST
    * Crossposted in FE_HELP

    27 Oct 23 02:51, Martin Kazmaier wrote to Tommi Koivula:

    24 Oct 23 11:25, Martin Kazmaier wrote to Wilfred van Velzen:

    @MSGID: 1:340/1101 01002731
    @PID: THE READER V4.50 [freeware]
    @NOTE: IceEdit 2.35 K96741
    @TID: FastEcho 1.46 43288

    There's no TZUTC kludge...

    I know, there's nothing I can do about that...

    Sure you can!

    The reader doesn't let me launch batch files as editors, so I
    can't
    use a batch file to force the TZUTC kludge into the message
    :(.

    You're using FastEcho, you can inject kludges to outbound
    messages when exporting. See external programs.. :)

    +======================== External programs
    ========================+ |
    | | After Unpack: d:\fastecho\afterunpack.cmd
    | | Before Pack: d:\fastecho\beforepack.cmd
    | |
    |
    +================================================================
    ===+

    Thanks Tommi! Now I need to see what to put in those batch files...

    I use sed in my 'beforepack.cmd'. :D

    === Cut ===
    for %a in (d:\fastecho\temp\out\*.qqq) (
    pktdate.exe -q -c -k -Lbeforepack.log %a
    sed -b -i -- 's/TID: FastEcho 1.46.1 1530
    )
    === Cut ===

    I don't know if there is sed for DOS.. But there is always a way. :)

    'Tommi

    --- FastEcho/2 1.46.1
    * Origin: =========================>>>> (2:221/1.254)
  • From Tommi Koivula@2:221/1.1 to Martin Kazmaier on Saturday, October 28, 2023 10:13:02
    * Originally in fe_help
    * Crossposted in fidotest

    Hi Martin.

    28 Oct 23 09:56:38, I wrote to you:

    I use sed in my 'beforepack.cmd'. :D

    === Cut ===
    for %a in (d:\fastecho\temp\out\*.qqq) (
    pktdate.exe -q -c -k -Lbeforepack.log %a
    sed -b -i -- 's/TID: FastEcho 1.46.1 1530
    )
    === Cut ===

    Hmm.. Something ate the end of my sed line...

    Lets try again:

    sed -b -i -- 's/TID: FastEcho 1.46.1 1530/TID: FastEcho 1.46.1 1530\x0D\x01HELLO: WORLD!/gi' %a

    'Tommi

    ---
    * Origin: Point One (2:221/1.1)
  • From Martin Kazmaier@1:340/1101 to Tommi Koivula on Monday, October 30, 2023 17:29:00
    * Originally in fe_help
    * Crossposted in fidotest

    Hi Martin.

    28 Oct 23 09:56:38, I wrote to you:

    I use sed in my 'beforepack.cmd'. :D

    === Cut === for %a in (d:\fastecho\temp\out\*.qqq)
    ( pktdate.exe -q -c -k -Lbeforepack.log %a sed -b -i -- 's/TID: FastEcho 1.46.1 1530 ) === Cut ===

    What is pktdate.exe? I couldn't find much about it. There is a vertraun
    entry for a y2k pkt fixer, but I'm not sure if that is this. I'm not
    familiar with sed, though I did find a win app for it, I'm at a loss as to
    how I should process *.qqq. I did find the proper directory, but think it's *.aaa. I can figure that out later, it's the parts I don't understand that
    I'm having problems with.



    Hmm.. Something ate the end of my sed line...

    Lets try again:

    sed -b -i -- 's/TID: FastEcho 1.46.1 1530/TID: FastEcho 1.46.1 1530\x0D\x01HELLO: WORLD!/gi' %a

    'Tommi

    --- * Origin: Point One (2:221/1.1)

    ---
    Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp)
    (ports 22, 23, 110, 21, 119) (ssh: login bbs password shsbbs)


    *** THE READER V4.50 [freeware]
    ---
    * Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (1:340/1101)
  • From Tommi Koivula@2:221/1 to Martin Kazmaier on Wednesday, November 01, 2023 08:36:32
    Martin Kazmaier wrote:

    What is pktdate.exe? I couldn't find much about it. There is a
    vertraun entry for a y2k pkt fixer, but I'm not sure if that is

    It can fix y2k date/time errors in outbound .pkt's. I have it in my FE setup because of a year 2020 bug in my bbs software, Concord.

    =============================================================================== Pktdate Rev. 1.4, written by Tobias Ernst @ 2:2476/418

    Usage: pktdate [<option> ...] <filename> [<filename> ...]

    Where <option> can be:
    -c Try to correct broken date fields in the PKT file. (The
    default is only to show those errors, but not to correct them).
    -l<loglevel> Set the maximum loglevel. <loglevel> can be:
    1 only log fatal errors
    2 log fatal errors and non-fatal errors (warnings)
    3 log errors, warnings, and information messages (default).
    4 also log debug information.
    -L<filename> Set the name and path of the log file. Default: no log file.
    -f<tolerance> Set the future tolerance for date field checking. A message
    date that is more than <tolerance> in the future will
    be considered broken and, if -c is specified be replaced by
    the current date. <tolerance> can be given in days, or
    in months by using the sufffix "m" like in "-f3m", or in years
    by using the sufffix "y". Default: 31 days.
    -p<tolerance> Works like -f, but specifies the tolerance into the past.
    Default: 364 days.
    -P<tolerance> Sets the past tolerance time for speculative error correction.
    Default: 1 month. See pktdate.txt for an explanation.
    -k When correcting errors, keep a copy of the original PKT.
    -q Accept Fastecho .QQQ style packet files.
    -S Change Seadog style date fields (like "Thu 1 Apr 99 10:05", a
    format that is deprecated) to the new FTSC format. ===============================================================================

    'Tommi

    ---
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)