PingPlotter Pro V3.10.0p - August 1st, 2006

Version 3.10.0p adds features and fixes problems found in the 3.00.2p release.

Download 3.10.0p from http://www.pingplotter.com/download.html.

3.10.0p changes:

• Significant enhancements to the remote agent capabilities, including a Windows agent. See here for details.
• Added two flags to web interface to allow read-only access and single-target access. Review Default.asp in /www/ directory of PingPlotter Pro for more details.
• Added an option (Edit -> Options, General) to show the setting name in most applicable areas (so tracing to the same target with different settings can now be differentiated).
• Added a column in the summary graph for the settings name (this defaults to off - you need to turn it on).
• A bunch of new content added to the help files (including the printable version).
• Saved images now include "ms" label on legend.
• Localized time formats should now be used on time graph (am/pm is no longer the only option).
• Added a new error handling system that provides a lot more information about problems.
• Right-clicking a tab now brings up a "Close" menu to close that tab.
• Right-clicking the "Settings" dropdown allows you to go directly to the properties from there.
• Exposed tray icon to scripting engine (we've written a script that uses this to show tray messages based on an alert event - you can get that from the new extensions forum).

Other Changes:

• Changed a bunch of core scripting engine systems to improve reliability.
• When shutting down a machine when running as a service, the PingPlotter service would sometimes be abnormally closed by Windows. Fixed.
• When running as a service under Windows 2003, the COM server would not serve objects. This made it impossible to use IIS as the web server.
• When running as a service, opening a file from a network drive did not work in some instances.
• When a non-current route was selected, a route change in the active network would cause the display to update - even though that wasn't the current route. Fixed.
• Fixed several bugs in the ability to load multiple sample sets and stitch them together.
• Added some capability to run as a service under Windows 9x. You'll need instructions and a couple of additional files for this to work, so contact us if interested.
• In some cases, certain status codes were being merged into the time-graph data, causing significant dips in the display. Fixed.
• If the email server blocked connection when testing, the error message now says that.
• If an invalid MIME type was configured in the registry (with a missing leading period), PingPlotter Pro could error on startup (and not start correctly).
• Fixed several minor memory leaks
• The service workspace could be specified without an extension, which caused the workspace to have a split personality.
• Fixed a problem that happened when a tab was closed while the summary graph was sorted - an access violation could occur.
• Deleting a named configuration while in use would cause problems. Now any targets using a deleted configuration use the default one instead.
• If a invalid or non-existent workspace was specified in the service startup parameters, PingPlotter Pro's startup would abort completely. Now it just shows an error.
• Graph images on non-Javascript web browsers would sometimes not show correctly in web interface.
• Some changes to built-in web server to improve reliability.
• 7 character HTTP server passwords would require an additional "g" character added at the end, if you wanted to log in (of course there was no way for you to know this!). 3 character passwords also had problems. Please reset your password after installing this new version if you were having problems with web interface passwords no longer working.
• Named configs didn't always get all settings applied when loading a workspace with targets that used a config that was non-default.
• Loading a sample set, then pausing and resuming worked fine, but doing it again would re-resolve and clear all history.
• Built in web server was stripping off "Option Explicit" from start of script, so customizing script could lead to problems.
• The summary graph didn't scale properly as new samples arrived. Now, the scaling is updated appropriately.
• The "Destination Unreachable" row didn't always show up at the end of a trace with a destination unreachable. Fixed.
• Fixed access violation that could occur when combining routes and then flipping through pages.
• Option dialog setting for disabling the script engine was ignored. Now disables all scripting.
• Lots of route changes (greater than 25,000) would cause the user interface to slow down (loading a sample set, or flipping between tabs). Can now handle 250,000+ route changes with no slowdown.
• Fixed "Not enough storage is available to process this command" on some (very few) Windows 2000 environments.
• Saving a sample set now writes it to a temporary file first. This can be useful if PingPlotter gets forcibly closed on shutdown - the last auto-save can be reloaded instead of the half-saved new file.
• Log entire route switch didn't work in "Log to file" alert events in some corner-case network conditions.
• When old samples were trimmed (because Max Samples in Memory was hit), any alerts that were in a firing state could possibly be toggled to not-firing, then back again, causing spurious "network back up!" events, then followed by "network down!" events.
• Access violation could occur when resetting data in an existing trace set.
• Fixed several bugs with route merging (list index out of bounds, inability to merge, display problems).
• ICMP raw socket packets could sometimes have interactions between PingPlotter instances.
• Several memory and performance optimizations / fixes.
• Fixed several access violations and odd errors.

For a list of changes to versions before 3.10.0p, see the 3.00 release notes.