PingPlotter Pro version 3.30.0p release notes
PingPlotter Pro V3.30.0p - September 28th, 2008
Click here to visit the 3.30.0p download page now.
This point release is free to all licensed users of PingPlotter Pro version 3.x.
Changes since 3.20.1
- 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.
- 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.
- A screenshot can now be included in alert emails (by adding ##SCREENSHOT## to email body).
- PRO ONLY - The configuration name can now be included in the alert email body (##CONFIG##), and in the subject line ($config).
- On some computers, the 30 day trial would expire the second time PingPlotter was run.
- /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.
- Email PingPlotter Support... menu option (under Help menu) has been streamlined.
- 10 character SMTP passwords weren't properly encrypted / decrypted, meaning you couldn't log in to your SMTP server if you're using a 10 character password with SMTP authentication.
- Uninstaller now supports the /S command line for silent removal of PingPlotter.
- PRO ONLY - The copy IP/Name right-click menu option wouldn't actually copy the information to the clipboard.
- 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.
For a list of changes to versions before 3.30.0p, see the 3.20 release notes.