Skip to content
Snippets Groups Projects
  1. Jan 21, 2016
    • rswindell's avatar
      Attempt to addres Bill McGarrity's reported error: · 8776b5e9
      rswindell authored
      2016-01-20 06:06:39 ERROR line 1836 renaming c:\fd\outbound\20060640.pk_ to
      c:\fd\outbound\20060640.pkt
      I think this is because the file 200606040.pkt already existed when the
      .pk_ temp file was created and thus the rename will fail (can't rename over
      an existing file) and then the packet is sent to the wrong link.
      When generating a packet name, keep incrementing until both the .pkt and
      .pk_ variants do not already exist. This should fix this scenario.
      8776b5e9
  2. Jan 20, 2016
  3. Jan 19, 2016
  4. Jan 18, 2016
  5. Jan 17, 2016
    • rswindell's avatar
    • rswindell's avatar
      I'm working on a major SBBSecho overhaul (to be dubbed version 3) and the old · 67f645ca
      rswindell authored
      sbbsecho.cfg file is going to be replaced with sbbsecho.ini. This script can
      be used to convert an existing sbbsecho.cfg (or other sbbsecho config file with
      a different filename) to an sbbsecho.ini (or other filename if desired). Either
      just run "jsexec sbbsecho_upgrade.js" or you can pass the cfg filename and the
      ini filenames on the command-line (e.g.
      jsexec sbbsecho_upgrade.js path/to/my/cfgfile path/to/my/inifile)
      
      Before I commit v3, I wanted to have some SBBSecho sysops give this converter a
      test run. The sbbsecho.ini file won't be used by anything today, I just want
      you to examine the resulting file or send it to me (with redacted pwds if you
      like).
      
      The objective is to retain all your settings (though some of them are going
      away, e.g. store_seenby, store_path, store_kludge, as these are just going
      be mandatory in future versions) but any comments you may have added by hand
      in your sbbsecho.cfg, unfortunately, won't be retained.
      
      On the bright side, the sbbsecho.ini *will* retain your comments when edited
      with the future version of echocfg and the modifications made via areafix won't
      be so damaging to any manual changes you've made.
      
      I hope you find the new config file easier to read and manage. I've tried to
      retain as many key-words as the old sbbsecho.cfg, so it should feel familiar.
      Feedback is welcome.
      67f645ca
  6. Jan 16, 2016
Loading