= = = = = = = = = = = = = = = = = = = = = =
The first time I ran the installer (jv16pt2008_setup_beta1.exe) to an empty preallocated folder, the program did not start when I clicked the Finish button.
An immediate rerun of the installer seems to have corrected the problem, whatever it was.
= = = = = = = = = = = = = = = = = = = = = =
This PT2007 problem still exists in PT2008. I reproduced the problem as follows:
2. Double click any item's line to get a "Show data" window
3. Drag as necessary to see the full title bar of both windows
4. Click in the middle of the title bar of one window, then click in the middle of the title bar of the other window
5. The resulting uncalled for window maximization is very disconcerting and a waste of user time to undo it
So far I've only tested it as described above, but I suspect every PT2008 window with the Minimize/Maximize or Restore/Exit widgets will have the same wasteful behavior. :(
BTW, the new main window GUI is quite nice. :)
= = = = = = = = = = = = = = = = = = = = = =
Suggestion:
The question popup (if needed as an "Are you sure?" measure) would only launch when one clicks that button. Alternatively, the click could just launch the system analysis directly avoiding the question dialogue altogether.
= = = = = = = = = = = = = = = = = = = = = =
The adverbial phase "mainly only" in the
= = = = = = = = = = = = = = = = = = = = = =
Using the following settings in v 1.7.0.416 finds the registry hive entries:
Search words:
Options: search only HKLM and only analyze key names
Ignore words:
With the same settings, PT2008 beta1 no longer finds the registry hive entries.
Note: The bug was apparently introduced in PT2007 v 1.7.0.422. It doesn't find the entries either.
= = = = = = = = = = = = = = = = = = = = = =
Some "file does not exist" error types are handled incorrectly by the "Fix manually …" feature.
The screenshot shows the situation.
When you click
2. causes a new erroneous entry to be put in the registry
3. does not correct the original error which stays in the registry
Notes:
PT2006 handles this type change correctly (it knows the data is data, not an entry name)
= = = = = = = = = = = = = = = = = = = = = =
Settings used:
Options: scan all the root keys and analyze key names, value names, and value data
With PT2007 (v 1.7.0.422), the search took just over two minutes.
With PT2008 beta1 (v 1.8.0.433), the search took considerably longer (about six times as long).
In this clickable graph, the PT2007 run is on the left; part of the PT2008 run is on the right:
Message box from the beta1 search:
: HKEY_CURRENT_CONFIG analyzed.
: HKEY_USERS analyzed.
: HKEY_CURRENT_USER analyzed.
: HKEY_LOCAL_MACHINE analyzed.
: HKEY_CLASSES_ROOT analyzed.
= = = = = = = = = = = = = = = = = = = = = =
