Does PowerTools 2010 crash?

leonardo

mallet wrote

Right click works for me too, with those three options marked.

But if I choose the five options (ie "click anywhere on a line...") it doesn't work! I think it should, what do you think ?

Yes, now I remenber, the "problem" occured when the option "click anywhere on a line to deselect" was check boxed!

Because when you want to RIGHT CLICK on a selected line this option forces an unwanted deselect of that line! Because you '"clicked anywere on that line'"!

So my conclusion at that time was "product works as designed", but do not activate setting: "click anywhere on a line to deselect"

mallet

thanks !

so that's a little bug according to me !

leonardo

mallet wrote

so that's a little bug according to me !

I do not think so, but let's wait on what the developer has to say about this.

leonardo

Leonardo wrote
Using XP-Pro-SP3 with jv16PT-2010-build 968:

1. The 'freeze' on the closure of jv16PTbuild968, right after using History Cleaner, is still there (repeatedly).

2. In History Cleaner, right clicking on line 'IIS Log Files' shows the two options "Explore' and 'Properties'.

Clicking option 'Properties' very often ends in an Access Violation (not always). Clicking option 'Explore' works OK!

I reported this already for XP-Pro-SP3 with build 968, but I can reproduce these application crashes/errors very easily in W7 x86 Professional too.

leonardo

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

siliconman01

Windows 7 x64 Professional, PT B968

The registry cleaner running from with jv16 main GUI has gone crazy again in the most aggressive setting. It finds 12350+ errors now. Clean and Fix in most aggressive finds 19 valid keys. RC at the default and next most aggressive finds only 5 errors.

siliconman01

Windows 7 x64 Professional, PT B968

In Clean and Fix, right click options are missing when examining a detected registry error item. For example, Open in Regedit is missing.

leonardo

siliconman01 wrote
Windows 7 x64 Professional, PT B968

In Clean and Fix, right click options are missing when examining a detected registry error item. For example, Open in Regedit is missing.

Confirmed for XP-Pro-SP3

siliconman01

Windows 7 x64 Professional, B968

Registry Cleaner crashes when Fixing registry detections. In this case, I was testing if RC detects an invalid RUN entry now. I placed a string value of SystemExplorer with a value of "" in the RUN key. RC detected the invalid RUN key. I selected the key and Open in Regedit so regedit was opened to the RUN key. Then I clicked on Fix in RC. The RC module crashed. This crash is 100% repeatable.

jv16

Leonardo wrote

Attached are two .zip files with the Bugreport.txt and Debug log.html of:

1. 'Freeze' at close of jv16PT build 968 after short usage of 'History Cleaner'.

2. 'Access Violation' after right clicking "Properties" on a line in 'History Cleaner'.

I was able to reproduce both of these issues and they should now be fixed. Thank you for reporting!

jv16

Leonardo wrote

I can invoke the problem rather easily by doing a partial fix+backup of the found errors in the 'result list' of the 'Registry Cleaner Scan'

This problem should also now be fixed, thank you for reporting!

jv16

siliconman01 wrote
Windows 7 x64 Professional, PT B968

In Clean and Fix, right click options are missing when examining a detected registry error item. For example, Open in Regedit is missing.

There has never been an "Open in RegEdit" item in the Right-Click menu of Clean and Fix my computer.

You can see all the available options from English.lng:



0 = Fix
1 = Remove
2 = Never show again
3 = Control hidden items
4 = Export as .reg file...
5 = Save as PowerTools backup file...

But there should be such a feature, therefore I did the following:

Improvement: In Clean and Fix My Computer, double clicking a registry item will now open it in RegEdit and double clicking a temp file item will open its folder in Windows Explorer.

jv16

siliconman01 wrote
Windows 7 x64 Professional, PT B968

The registry cleaner running from with jv16 main GUI has gone crazy again in the most aggressive setting. It finds 12350+ errors now.

There was a bug in the list component that caused it to count the number of items it holds incorrectly. So the Registry Cleaner found the exact same errors as in the previous build, but it reported the number of found errors wrong.

Fixed now.

jv16

A new preview build released:

http://www.macecraft.com/downloads/betas/jv16PT2010_build969.exe

If this solves all the Access Violation problems this build will be released officially tomorrow.

Here is the Change Log:

Bug fix: The program can randomly crash to List Index Out Of Bounds error when working with the result lists, such as with the results of the Registry Cleaner.


Bug fix: The program can randomly crash to Access Violation error when working with the result list.
Bug fix: Decrypt feature of File Tool's More Functions menu actually executes file Encrypt, not Decrypt.
Bug fix: In History Cleaner, if you double click an item, select the Files tab and select Properties from the Right-Click menu, nothing happens.
Bug fix: If you select not to install certain translations (e.g. Russian or Dutch), they are still installed to your system.
Bug fix: Some scan modules of the Registry Cleaner are not scanning the 64 bit side of the registry under 64 bit Windows.
Bug fix: Using the Right-Click menu's List Control features remove items from a result list can cause an Access Violation error.
Bug fix: The result lists of some tools, such as Clean and Fix My Computer, can contain duplicate groups, such as two "Temp files" groups.
Bug fix: The result list can show a negative number of selected items, for example: "Selected: -1, highlighted: 0, total: 10"
Bug fix: Closing the program right after opening a tool, such as the History Cleaner, can cause the program not to terminate properly.

Improvement: The installer will from now on remember its previous settings, so when installing the next update you will not have to make all the same changes again.
Improvement: The Registry Cleaner now finds more left-over data from old software.
Improvement: The installer now allows you to download translated versions of the Handbook, Danish and Dutch being the first available translations.
Improvement: Accessing and modifying the result lists is now faster, the list control is more responsive even with many items.
Improvement: In Clean and Fix My Computer, double clicking a registry item will now open it in RegEdit and double clicking a temp file item will open its folder in Windows Explorer.

New translations: Italian, Slovak.

Updated translations: Dutch, Russian.

I think you will like this, I think I got most of the things sorted out 8)

siliconman01

Windows 7 x64 Professional, PT B969

The most aggressive scan is still screwed up in B969. Pics are attached of B966 and B967. This is running RC from within jv16 main GUI.

siliconman01

Windows 7 x64 Professional, B969

Fix and Clean crashes on exit after "Fix" registry detections.

leonardo

XP-Pro-SP3 with build 968/969:

'Privacy Tools' -> 'History Cleaner' -> select 'Windows - Recent Documents' -> right click on the line -> select 'Show Data' -> right click on one of the lines displaying registry entries -> nothing happens. I expected two options 'Open in Reg Edit' and perhaps 'List control?'

Double clicking on the displayed registry entries executes 'Open in Reg Edit'.

Registry item_HistoryCleaner.jpg

siliconman01

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

jv16

siliconman01 wrote
Windows 7 x64 Professional, PT B969

The most aggressive scan is still screwed up in B969. Pics are attached of B966 and B967. This is running RC from within jv16 main GUI.

From the screenshots, it looks like the B969 is listing a lot of data twice, is this correct?

siliconman01

jv16 wrote
siliconman01 wroteWindows 7 x64 Professional, PT B969

The most aggressive scan is still screwed up in B969. Pics are attached of B966 and B967. This is running RC from within jv16 main GUI.

From the screenshots, it looks like the B969 is listing a lot of data twice, is this correct?

It does appear that way...plus they are invalid detections in the ActiveX/DCOM area. I've attached a listing of the keys

« Previous Page Next Page »