PingPlotter Standard version 3.20.2s beta 2 - July 16th, 2008

This beta version requires a valid PingPlotter Standard license key to function. If you're looking for the evaluation version, please download the latest full release.

The download link for this beta is at the bottom of this page.

Changes since 3.20.2s beta 1

• STANDARD ONLY: Some old PingPlotter Standard license keys didn't work correctly (issued in 1998 and early 1999).
• Trace scheduler would sometimes "lose track" of a target when adding a bunch of targets at once. This usually manifested itself in Pro when loading a workspace with a lot of targets - some of the targets might not start tracing.
• Removed some debugging code that was causing extra CPU load on some systems.

PingPlotter Standard version 3.20.2s beta 1 - July 8th, 2008

Changes since 3.20.1s

• Added a "Don't Fragment" flag to allow PingPlotter to help with MTU size troubleshooting.
• TCP Traceroute is now more robust. Packet sequence numbers was also changed to make it better supported by servers.
• "Launch an Executable" event now has separate parameter line, and is more flexible and reliable.
• Screenshots can now be included in alert emails by adding a ##SCREENSHOT## variable to the message body.
• PRO ONLY - Saving a workspace can now include collected data. Reloading it will reload (and resume) tracing. Check the general settings (Edit -> Options, General) for some new options.
• PRO ONLY - Workspaces are now "locked" for writing so that multiple instances of PingPlotter Pro don't accidentally overwrite settings.
• PRO ONLY - Alerts can now be associated with a specific trace target only. This allows better monitoring of intermediate routers on one trace while not monitoring that same router on another trace. Also, the same target can have different alerts (say, for instance, if you're using a different trace engine and the expected latency / packet loss is different, even though the target is the same).
• PingPlotter would sometimes freeze when a float-over tooltip was visible and a certain part of the PingPlotter user interface was clicked at just the right time.
• Sending an email with data (File -> Send Email...) wouldn't work if there was an invalid character in the host name (like an *).
• PingPlotter would sometimes crash when loaded (on just a few computers) due to problems with the integrity checking logic.
• /Regserver command line option didn't fail gracefully during install.
• Some truncated / corrupt save files wouldn't show a proper error message when attempting to load.
• PRO ONLY - Remote trace wouldn't take advantage of Proxy server settings.
• PRO ONLY - Closing the summary graph and then clicking the "File" menu could cause an access violation.
• PRO ONLY - PingPlotter Pro would sometimes trace twice in the same target interval.
• STANDARD ONLY - When the trial period expired with PingPlotter Standard, double-clicking on a .pp2 file would cause an error.
• STANDARD ONLY - In PingPlotter Standard, maximizing the window, then closing and reopening would cause the window to come up the wrong size and position.
• Several other bug fixes / tweaks.

As with all recent PingPlotter betas, a valid license key is required to run this beta (i.e.: any licensed user is welcome to try out this version).

To see previous release history, please visit our online release notes.