jv16 PowerTools 2010 Beta1 released!

tlstevens

When running registry cleaner, the resulting list text isn't as clear as in jvpt 2009. It is smaller and the font makes it harder on the eyes to read.

Another thing with registry cleaner is that items found under invalid file references for the documents folder doesn't show the whole file path in the file reference field.

Power tools image.jpg

shorto

I miss the threads remaining feature during a search. "Don't know if I have time to get a Coffee refill or not!" - - - Shorto :

doogie

siliconman01 wrote
Windows 7 x64 Professional.

In the Startup Manager, if you right click or Back click on the vacant area below the program list, jv16 causes an access violation.

Yes I can confirm this running Windows 7 x64.

: Access violation at address 00719E31 in module 'jv16PT.exe'. Read of address 0000001C

redseujac

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.

mauricev

On installing beta1, I saw the post of an illegal instruction, though it appeared to continue the installation successfully.

In running it the first time, the analysis took at least 10 minutes perhaps more. The main screen doesn't get updated frequently enough I don't think and it's not clear why it needs so much time to do this. Is this debug code?

I ran this on a system with infamous "ignore the Fix button" bug in 2009, http://www.macecraft.com/phpBB3/viewtopic.php?f=21&t=3922, and this version is no different. The bug is still present. As in many cases, it starts, but then soon fails with an invalid pointer error.

leonardo

Previous jvPT2009 minor-bug is back again:

First start jv16PT_2009_v606 after that start jv16PT2010_beta (only in this sequence!). Stopping jvPT2010 will also close the earlier started jv16PT2009_606.

redseujac

mauricev wrote
...In running it the first time, the analysis took at least 10 minutes perhaps more. The main screen doesn't get updated frequently enough I don't think and it's not clear why it needs so much time to do this. Is this debug code?...

"Initial Setup" makes also backups of essential parts of the registry and saves them to harddisk. You can restore them if necessary via the Backup Tool > Tools > System Recovery. This happens only once, i.e. the first time you run the program after installation.

tlstevens

Windows not maintaining size when minimized and reopened. Ran fix my computer app maximized window, minimized to taskbar, when i reopen the window it defaults to its original size.

tullik

47. Clean and fix my computer: List control-->Remove from list for the MRU and history data group causes a PowerTools hang every time. I'll post a debug log separately.

C&FMC hang with remove from list.zip

tullik

From my perspective, there are at present 50 to 52 issues in Beta 1 that will carry forward to Beta 2.

The issues are listed here:

http://www.macecraft.com/phpBB3/viewtopic.php?p=22138#p22138

http://www.macecraft.com/phpBB3/viewtopic.php?p=22129#p22129

About eleven of these are from pre-beta test versions.

doogie

tullik wrote
47. Clean and fix my computer: List control-->Remove from list for the MRU and history data group causes a PowerTools hang every time. I'll post a debug log separately.

C&FMC hang with remove from list.zip

I can't replicate that here tullik. Running Windows 7 x64.

tullik

DooGie wrote
tullik wrote
47. Clean and fix my computer: List control-->Remove from list for the MRU and history data group causes a PowerTools hang every time. I'll post a debug log separately.

C&FMC hang with remove from list.zip

I can't replicate that here tullik. Running Windows 7 x64.

It happens every time with an x64 Vista desktop, an x86 Vista desktop, and an x86 Windows 7 notebook. I don't have an x64 Windows 7 system.

leonardo

DooGie wrote
tullik wrote
47. Clean and fix my computer: List control-->Remove from list for the MRU and history data group causes a PowerTools hang every time. I'll post a debug log separately.

C&FMC hang with remove from list.zip

I can't replicate that here tullik. Running Windows 7 x64.

Running XP with SP3 I can easily reproduce this on both my laptop and desktop. Not only for the "MRU and history data group" but for other groups as well.

siliconman01

Windows 7 x64 Professional

I put the Registry Scanner in Reference mode at the most aggressive setting. I just wanted to see what it would find. The scan hangs indefinitely at what appears to be end of the scan. A debug log is attached.

jv16

siliconman01 wrote

This is on Windows 7 32-bit Professional. Registry scanner is set to 3rd level of aggression. They also show up in the most aggressive level.

The scanner is misreading these five keys concerning the Intel Matrix Storage Manager uninstaller.

The directory and the files do in fact exist on this system.

This bug should now be fixed. I have verified the fix with synthetic data myself but could you please verify the issue with the Beta2 and report back to me?

Also, I have created a simple way for you to check it: With beta2, go to the Main Window's Debug Menu, from there select "siliconman01: Shell_ENU test". It runs this data (with few variations) with the registry cleaner engine.

jv16

DooGie wrote
I mean the window in focus at the time of scanning Jouni.

Can you, or someone else, give me steps how to reproduce the issue?

I did the following:

1. Start the Registry Cleaner, let it complete.

2. Resize the results window.

3. Close PowerTools

4. Start PowerTools, Start the Registry Cleaner, let it complete.

And the window size was the same I last resized it to.

tullik

siliconman01 wrote
Windows 7 x64 Professional

I put the Registry Scanner in Reference mode at the most aggressive setting. I just wanted to see what it would find. The scan hangs indefinitely at what appears to be end of the scan. A debug log is attached.

Tested on x64 Vista HP SP2 desktop

I hadn't tried the reference scanning mode, so I did it too. It completed normally. However, when compared to the same aggressive scan with normal scanning mode, there were some differences in the Invalid file or directory reference group:

Normal mode:
- The list showed 80 lines.
  
  There were no "false positives."
Reference mode:
- The list showed 167 lines.
  
  There were about 5 possible "false positives," all related to incorrect handling of Wow6432Nodes.
  
  I'll pick those out and add the information to this post in case Jouni wants to reproduce the result.
  
  There were also 41 suspicious lines for a CLSID. It's too complex to post here. I'll check it again in Beta 2.

Possible false positives from the list:

jv16 PowerTools 2010 ; Note: the correct subkeys and entries are under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\... Data fields are: Key, Entry's name, Value, Entry last modified, Error severity, Error description, File reference HKLM\Soft\MSoft\Win\CurVer\SharedDLLs\, C:\Windows\system32\mscomctl.ocx, N/A, 09.12.2009, 20, 99, File or directory "C:\Windows\system32\mscomctl.ocx" does not exist, C:\Windows\system32\mscomctl.ocx HKLM\Soft\MSoft\Win\CurVer\SharedDLLs\, C:\Windows\system32\VEN2232.OLB, N/A, 09.12.2009, 20, 99, File or directory "C:\Windows\system32\VEN2232.OLB" does not exist, C:\Windows\system32\VEN2232.OLB HKLM\Soft\MSoft\Win\CurVer\SharedDLLs\, C:\Windows\system32\VBAEND32.OLB, N/A, 09.12.2009, 20, 99, File or directory "C:\Windows\system32\VBAEND32.OLB" does not exist, C:\Windows\system32\VBAEND32.OLB HKLM\Soft\MSoft\Win\CurVer\SharedDLLs\, C:\Windows\system32\VBAEN32.OLB, N/A, 09.12.2009, 20, 99, File or directory "C:\Windows\system32\VBAEN32.OLB" does not exist, C:\Windows\system32\VBAEN32.OLB

HKLM\Soft\MozillaPlugins\@adobe.com/FlashPlayer\, XPTPath, C:\Windows\system32\Macromed\Flash\flashplayer.xpt, 24.11.2009, 07, 99, File or directory "C:\Windows\system32\Macromed\Flash\flashplayer.xpt" does not exist, C:\Windows\system32\Macromed\Flash\flashplayer.xpt

Entries.reg for them using the Registry Cleaner context menu:

Windows Registry Editor Version 5.00

; File created by TBackupTool
; Component version: 1.4.2
; Component used by: jv16 PowerTools 2010
; Program version: 2.0.0.644
; File Description: 
; Date: 11.12.2009
; Time: 05



"C:\\Windows\\system32\\VBAEN32.OLB"=dword
"C:\\Windows\\system32\\VBAEND32.OLB"=dword
"C:\\Windows\\system32\\VEN2232.OLB"=dword
"C:\\Windows\\system32\\mscomctl.ocx"=dword


"XPTPath"="C:\\Windows\\system32\\Macromed\\Flash\\flashplayer.xpt"

Note: all the above referenced files exist, so reproduction in a test environment could require creation of fake files with the referenced names.

jv16

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

tullik wrote

2. Clicking the main window's "Live Support” icon resizes the open Firefox window to an inconveniently small size. || 644 x64

This is caused by the Live Support service provider, they resize the browser window, not PowerTools. So I'm afraid there is nothing we can do about that.

tullik wrote

3. Registry Information: the window is a little too small. The sixth stored data type (“Other”) is not fully visible. || 644 x64

Could I get a screenshot of this issue?

tullik wrote

17. Registry tools such as the Registry Finder can show duplicate data under 64 bit Windows. || 642 (???) x64 || 644 (???) x64

To be clear, does Registry Finder show all the results twice, or just some? Could you also send me a screenshot of this issue? I'd like to check something else too.

jv16

redseujac wrote
siliconman01 wroteIn the Registry Cleaner, the "Export as .reg file" does not work on Win 7 x64 Professional. The navigation window does not open to select where to export it to. It does work on Win 7 x86 Professional.

Release Notes:

* All features that requires the user to select a file using the Windows Open or Save To dialog such as "Save List As", "Export to .Reg" etc. do not always work with 64 bit Vista. This is a bug in Vista, not in PowerTools.

Maybe it doesn't work in Windows 7 64-bit either, although I'm under the impression that the "bug" in Vista had been fixed in Win7?

It seems the issue is still present with 64 bit Windows 7. I'll try to find a workaround to this issue, maybe use differen API calls or something.

« Previous Page Next Page »