Hermes II 3.5.9

Hermes II 3.5.9 is the final release of the 3.5.9 beta codeline. This version adds built-in TCP/IP connectivity, integrated FidoNet support, Y2K compatibility, and improved stability over the 3.5.8 version. In addition, functionality to enable the new Java-based External Development System is now part of the core BBS.

All SysOps should upgrade to the 3.5.9 version to improve the stability and performance of their systems. SysOps that are not using the built-in FidoNet support should not upgrade to 3.5.9 as it does not support external FidoNet processors. A special version of the FidoNet external will soon be released for SysOps that require this functionality.

Beta Changelog

Major features added in 3.5.9b3:

• Hermes II can now support up to 50 nodes using a special version of the BBS application. Data files are not compatible between the two versions. This version is available by special request only.

Minor features added in 3.5.9b3:

• Telnet negotiation is now much faster.

Bugs fixed in 3.5.9b3:

• Fixed various crashing bugs introduced in previous beta versions.

Major features added in 3.5.9b2:

• FidoNet support
  Direct support for FidoNet is now available via the Hermes II FidoNet external. Combined with the changes to the Hermes II BBS itself, the FidoNet external completely replaces the Generic Import/Generic Export system. For more information, see the documentation that comes with the FidoNet external.
  Please note that gating of Internet mail through FidoNet is no longer automatic. You can still use FidoNet<->Internet gateways, but you must address the message yourself.

• Hermes API Hooks
  Hooks have been added to the Hermes II BBS to allow the new Hermes API Runtime to support externals written with the External Development System. The EDS will be made available later in the beta cycle.

Minor features added in 3.5.9b2:

• Hitting \ when reading a FidoNet message will re-read the message with all FidoNet control characters and SEEN-BY lines shown.
• Screensaver status information is now displayed in two lines and uses the same size font that the node informationd display uses.
• The e-mail list screen is now displayed in color.

Bugs fixed in 3.5.9b2:

• Do not let SysOps use the 'V'alidate option when reading NetMail.
• Change //SORT algorithm to work better on mostly-sorted directories.

Hermes II 3.5.9b1.1

Hermes II 3.5.9b1 is a minor beta release made available fix the Y2K bugs in Hermes II 3.5.9b1. These bugs have all been fixed in 3.5.9b2, but as that version is not yet available, we felt it was necessary to issue a Y2K patch release until the full 3.5.9b2 version is ready.

Major features added in 3.5.9b1.1:

Minor features added in 3.5.9b1.1:

Bugs fixed in 3.5.9b1.1:

• Fix Y2K problems in the Generic Export code. Two-digit years were being written as three-digit years.
• Fix Y2K problems in //QSCAN, age calculation, and file limits. These prompts now accept '00' as a valid year. Age calculation will break for users who were born before 1906 as well as users born after 2005. These problems will be fixed in a later release.
• Fix UEDIT so that it doesn't try and write invalid users. Entry into UEDIT from the Main Menu (//UEDIT) and from the 'V'alidate User option in EMail do not cause UEDIT to write out the current user before selecting the new user to edit.

Hermes II 3.5.9b1

Hermes II 3.5.9 is the first TCP/IP aware version of the Hermes II BBS program. By using the TCP/IP node type, you can allow callers to access your BBS over the Internet using the Hermes II Terminal or a compatible telnet application.

Major features added in 3.5.9b1:

• TCP/IP login
  If you select the "TCP/IP" node type in the Node Preferences window, the Hermes II software will begin listening for telnet connections on TCP/IP port 23. You can create as many TCP/IP nodes as you like (up to the system limit of 10 nodes). Each TCP/IP node will allow one caller to log in via telnet at a time. All TCP/IP nodes will listen for connections on the same port (port 23).

• Color changes
  User colors and system colors have been better defined. Previously, users had complete control over the colors that they saw when using the BBS. This is no longer the case. The user colors (0-F) are now for message use only. The system colors (Normal, Prompt, Yes/No, etc.) have been moved into a SysOp-only //COLORS menu and affect all users.

  In addition to this change, the old-style Ctrl-C menu colors (the ones that used the 0-F user color codes) are no longer supported. Instead, you should use the new-style shortcuts defined below:

  <Ctrl-C>FBIUB
  F = Foreground color (0-7)
  B = Background color (0-7)
  I = Intense ('T' = intense; 'F' = normal)
  U = Underline ('T' = underline on; 'F' = underline off)
  B = Blinking ('T' = blink; 'F' = no blink)

  The ANSI colors are: 0 - black, 1 - red, 2 - green, 3 - brown, 4 - blue, 5 - magenta, 6 - cyan, 7 - gray. When combined with the intense attribute, the colors are: 0 - lt.gray, 1 - lt.red, 2 - lt.green, 3 - yellow, 4 - lt.blue, 5 - lt.magenta, 6 - lt.cyan, 7 - white.

  If you have files and/or HTxt's that need to be converted from the old format to the new format, you can use the Color Converter utility available on the FTP site at ftp://ftp.HermesII.org/pub/HermesII/utilities/Color Converter 0.92.sea.hqx to automatically convert all of your ANSI texts.

Minor features added in 3.5.9b1:

• Quitting from the sub-conference Q-Scan default now puts you back at the forum menu rather than the Defaults menu. Pressing 'Q' is now a valid way to exit the forum menu.
• SysOps are visible in the Who's On Line menu, although non-SysOps don't get to see what the SysOps are doing.
• The local terminal's colors have been updated to reflect those used in the Hermes II Terminal.

Bugs fixed in 3.5.9b1:

• Message, text, etc. listings were counting the numbers of lines they had displayed incorrectly. The result was that the top line of each 'page' of text would scroll of the screen.
• Only the first 8 characters of the serial number are displayed in the about box.
• Clicking in a non-editable text window (logs, for example) caused Hermes II to crash.
• OutLineSysop was using bCR to send carriage returns; this meant that the user, not the SysOp, was getting a carriage return.