1. 02 Mar, 2022 2 commits
  2. 07 Oct, 2021 1 commit
  3. 06 Oct, 2021 1 commit
    • Rob Swindell's avatar
      Don't append the stale static string in fmsgattr_str() · bb0d2496
      Rob Swindell authored
      When this function was called multiple times (e.g. multiple messages in a pkt),
      it would keep appending to the current (static) string, eventually overflowing
      the buffer and corrupting the stack. Although reported in pktdump, it could
      have also happened with fmsgdump if passed multiple stored message (.msg) files.
      Fixes #295 reported by Nelgin
  4. 11 Mar, 2021 1 commit
    • Rob Swindell's avatar
      Fix issue display AREA keywords at beginning of body text · 64b754a3
      Rob Swindell authored
      or any lines that were only terminated with carriage-return (\r)
      since these are treated rather-oddly by the FTN software as a
      line-ending and line-feeds are to be ignored. So transfer \r to \n
      on output and ignore the \n's in the body text.
  5. 15 Feb, 2021 2 commits
  6. 16 Aug, 2020 1 commit
  7. 28 Apr, 2020 1 commit
  8. 26 Apr, 2020 1 commit
  9. 09 Apr, 2020 3 commits
    • rswindell's avatar
      Added new option -split, which will split a packet into a *.good and a *.bad · 999563c7
      rswindell authored
      file containing only the good or bad messages, leaving the orignal *.pkt file
      The -recover option will *only* create a *.good file (renamed from .recovered).
      Now, if the recovered (good) or bad output file has no messages or is the exact
      same size as the original pkt file, the output file is automatically deleted.
    • rswindell's avatar
      If a pkdmsg type is not 0x0002, then just move forward 2-bytes until there is · 96d27072
      rswindell authored
      valid pkdmsg type.
      This will allow better re-sync with a badly corrupted packet.
      I waffled about whether it should try to read the variable header fields if the
      DateTime field of the fixed header is invalid. Currently, it does. The pkdmsg
      header does not have very good identifying marks to re-sync with, so it's
      still possible that a valid msg that follows a corrupted one could get skipped.
      I would need some good set of varying examples of corrupted packets to test
      with, but I'm sure it's possible to "do better".
    • rswindell's avatar
      Added a -recover option (e.g. pktdump -r *.pkt). This option will create · 68947da2
      rswindell authored
      duplicates of all the parsed packet files, but excluding all corrupted packed
      messages. The recovered packet files are named *.recovered.
      Also improved the corrupted packed message header detection to make this
      feature more useful.
      Created at the request of Nelgin who promises to test and use, for better or
      for worse, in sickness and in health, from this day forward, yadda yadda yadda.
  10. 08 Oct, 2018 1 commit
  11. 31 Mar, 2018 1 commit
  12. 25 May, 2016 2 commits
  13. 05 Oct, 2013 1 commit
    • rswindell's avatar
      Output product/revision information. · 49b28fe0
      rswindell authored
      Print wanring if type 2+ orig/dest zones don't match the zone fields in the
      type-2 portion of the header.
      Updated some pkt header field names in fidodefs.h.
  14. 17 Sep, 2013 1 commit
  15. 13 Oct, 2012 1 commit
  16. 27 Jan, 2010 1 commit
  17. 15 Jan, 2009 2 commits
  18. 07 Jan, 2007 1 commit
  19. 28 Dec, 2006 1 commit