jv16 PowerTools 2010 Beta4 released!

tullik

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.

[deleted]

Sorry for not having posted much, but I'm having trouble accessing our x64 testing machines so I've not been able to confirm most of the serious bugs being talked about.

tullik wrote

The Debug Report for the "one session" shows this:

Windows version = 5.1.2600

Windows 7 = False

The Debug Report normally shows this:

Windows version = 6.1.7600

Windows 7 = True

That's very odd. I'm assuming you didn't run PT in compatibility mode or otherwise differently than usual?

tullik

hukka wrote
...
tullik wrote

The Debug Report for the "one session" shows this:

Windows version = 5.1.2600

Windows 7 = False

The Debug Report normally shows this:

Windows version = 6.1.7600

Windows 7 = True

That's very odd. I'm assuming you didn't run PT in compatibility mode or otherwise differently than usual?

That was it. Thanks. That specific jv16PT.exe instance got that way from using the windows "Troubleshoot compatibility" option.

I'll remove the material observed while the compatibility setting was active to avoid confusing others.

Without the compatibility setting, the other behavior still occurs as described here: http://www.macecraft.com/phpBB3/viewtopic.php?p=22589#p22589

I retested it and the phenomenon is still repeatable.

redseujac

siliconman01 wrote
..it would be rather premature to issue a RC1 next (after the current Beta 4)....

If u are serious about not repeating the unfortunate mistakes of the recent past, then Please lets have patience & Please release at least 1 or more additional Betas.

Yes, I agree. RC status is a bit premature considering we do not even have Registry Compact for Windows 7 yet and such things as the Age/Comment component has not been tested....plus all the current fix items needed. More Beta testing needed before RC status.

I do agree also...

RC1 will come too early.

The developer has pledged to make version 2010 fully compatible with Windows 7 64-bit. So all parts of the program should run with that OS, Registry Compactor inclusive.

tullik

These issues, from before Beta 4, had been confirmed to still exist when using x64 Windows 7.

They have now been confirmed also to exist when using x86 Vista.

Note: most reference links were made not hot to work around a board limit in the number of URLs in a post.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

33. When you save a named preference, it saves OK. However, the name shown in the box immediately changes to “Saved preferences ...” – IMO, the just saved name should show instead.

More info: this has been around since the “Pre-beta”

Reference: <http://www.macecraft.com/phpBB3/viewtopic.php?p=22558#p22558>

12. Startup Manager: create new to HKCU RunOnce works, but the task never shows in the list.

More info: this is from Beta 1 – the bug also exist with x86 Vista.

14. Backup tool: when restoring multiple backups at the same time, if some have the same description, some of those do not restore (per the messages).

More info: this is from Beta 1 – the bug is also on x86 Vista.

Reference: <http://www.macecraft.com/phpBB3/viewtopic.php?p=22576#p22576>

29. File Tools (various): Size and Dates, when preferred columns, often do not fill in until you deselect Size. Then you have to reselect Size to make it show. It is more likely to happen with a large list.

More info: this is from Beta 1 – the bug is also on x86 Vista.

45. File Recovery Tool: results window shows no action buttons and the Top Panel and status bar are blank.

More info: this is from Beta 1 – the buttons show on x86 Vista, but the tool can crash all of PowerTools there.

46. File Recovery Tool: when you select a file, use the right click “Undelete” option, and choose a target directory, nothing happens.

More info: this is from Beta 1 – I don't know if behaves the same on x86 Vista. The tool has too many other issues to tell.

68. Backup Tool, Custom Restore: when switching between the Files and Registry tabs, the column widths are forgotten.

More info: this is from Beta 2 – this bug is the same on x86 and x64 systems.

70. Live support tool: the Abort button stays red (the other two buttons turn green).

More info: this is from Beta 3 – this bug is the same on x86 and x64 systems.

Reference: <http://www.macecraft.com/phpBB3/viewtopic.php?p=22551#p22551>

90. Clean & fix my computer: is not honoring the “Never show” again list.

More info: this is from Beta 3 – It also doesn't work on an x86 Vista system.

91. File Recovery: can get an access violation. If the scan is aborted, the violation can occur several minutes later.

More info: this is from Beta 3 – behavior changed with fixes in Beta 4, but the tool is still unstable on both x86 and x64 systems.

92. Desktop shortcuts: History Cleaner (for example) does not use the remembered column widths when started this way.

More info: this is from Beta 3 – It has the same problem on x86 Vista.

108. Custom Restore: has “Open in RegEdit” in the context menu for a file.

More info: this is from Beta 3 – just menu fine tuning regardless of the windows system type,

3. Live support tool: the Abort button stays red (the other two buttons do turn to green after click).

X86 and x64 both have this bug.

Reference: <http://www.macecraft.com/phpBB3/viewtopic.php?p=22551#p22551>

10. Filter Panel can sometimes pop up outside of the list control.

This bug is there with x86 and x64.

Reference: <http://www.macecraft.com/phpBB3/viewtopic.php?p=22569#p22569>

18. The new tool tips are not in use in the list components, except for the columns.

In Beta 4, the tool tips are gone on both x64 and x86 systems.

Reference: http://www.macecraft.com/phpBB3/viewtopic.php?p=22567#p22567

39. Aborting a registry snapshot creation (with the Registry Monitor tool) can crash the program. Also, the operation can continue to run in the background.

On both x86 and X64.

Reference: <http://www.macecraft.com/phpBB3/viewtopic.php?f=10&t=4025&p=22548&hilit=Search%E2%80%A6Registry+Monitor+Compare#p22548>

40. Aborting Registry Monitor's Compare feature incorrectly shows the "Operation completed, following changes were detected..." message and the actual operation can continue to run in the background.

On both x86 and X64.

Reference: same as #39.

49. Using the mouse wheel or the scroll area of a laptop, it is possible to make the Main Window get stuck in a very long scrolling loop where the category selector on left keeps moving rapidly.

This happens on both x64 and x86 systems.

Reference: <http://www.macecraft.com/phpBB3/viewtopic.php?p=22531#p22531>

65. It's possible to create a new automated task that doesn't do anything.

Prior=Beta 3.

Reference: http://www.macecraft.com/phpBB3/viewtopic.php?p=22572#p22572

27. File Encrypter: it seems the feature doesn't show an Abort button or any sort of progress indicator. I was encrypting over 1300 file from the File Tool.

Prior=Beta 2

32. Delete of a selected item in the Registry Manager "Open with" tab dropped the item from the list but backed up and deleted nothing.

Prior=before the Pre-Beta

34. When you delete an HKCU item and its HKUS “mirror” with Custom Fix, one of the items stays in the results list.

Prior=before the Pre-Beta

41. Main window statistics says “... fixed 695 registry errors and deleted 51 temp files, 5 files deleted in total.” which is contradictory. It should say, for example, “... fixed 695 registry errors, deleted 51 temp files, and deleted 5 other files.”

Prior=the Pre-Beta

47. Clean and fix my computer: List control-->Remove from list for the MRU and history data group causes a PowerTools hang every time.

Prior=Beta 1

49. Clean and fix my computer: MRU in the Ignore words tab does NOT prevent the MRU and history data group from appearing in the results.

Prior=Beta 1

50. Automation Tool: when running tasks from the list, the “Last run” date is not updated in the list until you close and reload the list.

Prior=Beta 1

tullik

The structures below exist in the registry.

Registry Cleaner evaluates them as "Obsolete Software entry."

However, what shows in the GUI does not all correspond to what is actually in the registry. Furthermore, the file "C:\Windows\INF\oem11.inf" does exist.

Could the "not Wow6432" items be a false positive?

Realtek Semiconductor Corp. not W6432.regWindows Registry Editor Version 5.00






"install"="success"
"OemInf"="C:\\Windows\\INF\\oem11.inf"

"version"="6.0.6000.20096"

Realtek Semiconductor Corp.is Wow.regWindows Registry Editor Version 5.00

tullik

139. Registry Cleaner: access violation while examining a probable false positive situation in a four line list. {.} 686 x64 w7

*Reg Clnr violation.zip

These were the four lines. Invalid file or directory reference



 HKCR\CLSID\{DFA14C43-F385-4170-99CC-1B7765FA0E4A}\InProcServer32\ @ C:\Windows\SysWOW64\wpcumi.dll 22.01.2010, 16 99 File or directory "C:\Windows\SysWOW64\wpcumi.dll" does not exist C:\Windows\SysWOW64\wpcumi.dll

 HKCR\Wow6432Node\CLSID\{DFA14C43-F385-4170-99CC-1B7765FA0E4A}\InProcServer32\ @ C:\Windows\SysWOW64\wpcumi.dll 22.01.2010, 16 99 File or directory "C:\Windows\SysWOW64\wpcumi.dll" does not exist C:\Windows\SysWOW64\wpcumi.dll

 HKLM\software\classes\CLSID\{DFA14C43-F385-4170-99CC-1B7765FA0E4A}\InProcServer32\ @ C:\Windows\SysWOW64\wpcumi.dll 22.01.2010, 16 99 File or directory "C:\Windows\SysWOW64\wpcumi.dll" does not exist C:\Windows\SysWOW64\wpcumi.dll

HKLM\software\classes\Wow6432Node\CLSID\{DFA14C43-F385-4170-99CC-1B7765FA0E4A}\InProcServer32\ @ C:\Windows\SysWOW64\wpcumi.dll 22.01.2010, 16 99 File or directory "C:\Windows\SysWOW64\wpcumi.dll" does not exist C:\Windows\SysWOW64\wpcumi.dll

This is what a custom program backup did.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.686
; File Description: DFA14C43-F385-4170-99CC-1B7765FA0E4A
; Date: 22.01.2010
; Time: 14


@="C:\\Windows\\SysWOW64\\wpcumi.dll"


@="C:\\Windows\\SysWOW64\\wpcumi.dll"


@="C:\\Windows\\SysWOW64\\wpcumi.dll"
@="C:\\Windows\\SysWOW64\\wpcumi.dll"

@="C:\\Windows\\SysWOW64\\wpcumi.dll"

This is what the registry actually contained for the CLSID (a consolidation of 5 separate RegEdit exports). DFA14C43-F385-4170-99CC-1B7765FA0E4A.regWindows Registry Editor Version 5.00




@="C:\\Windows\\System32\\wpcumi.dll"
"ThreadingModel"="Apartment"


@="C:\\Windows\\SysWOW64\\wpcumi.dll"
"ThreadingModel"="Apartment"


@="C:\\Windows\\System32\\wpcumi.dll"
"ThreadingModel"="Apartment"


@="C:\\Windows\\SysWOW64\\wpcumi.dll"
"ThreadingModel"="Apartment"


"ThreadingModel"="Apartment"

@="C:\\Windows\\SysWOW64\\wpcumi.dll"

This is a backup created by Delete.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.686
; File Description: DFA14C43-F385-4170-99CC-1B7765FA0E4A
; Date: 22.01.2010
; Time: 14



@="C:\\Windows\\SysWOW64\\wpcumi.dll"

@="C:\\Windows\\System32\\wpcumi.dll"

C:\Windows\SysWOW64\wpcumi.dll does not exist.

C:\Windows\System32\wpcumi.dll does exist.

There are multiple bugs in this case. To summarize:

*** Some items in the GUI differ from the registry content.

*** The custom backup is incorrect. That is, it wold not restore what the program would remove. It also contains a minor name=value error, harmless in this case.

*** The program removes a reference to an existent system32 dll which is not even shown in the GUI.

*** The backup with fix or delete seems to vary randomly. Some of the variations would not restore the prior state.

Here are several of the variations:

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.686
; File Description: DFA14C43-F385-4170-99CC-1B7765FA0E4A
; Date: 22.01.2010
; Time: 14



@="C:\\Windows\\SysWOW64\\wpcumi.dll"


@="C:\\Windows\\SysWOW64\\wpcumi.dll"


@="C:\\Windows\\SysWOW64\\wpcumi.dll"
@="C:\\Windows\\SysWOW64\\wpcumi.dll"


@="C:\\Windows\\SysWOW64\\wpcumi.dll"
==================================================
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.686
; File Description: DFA14C43-F385-4170-99CC-1B7765FA0E4A
; Date: 22.01.2010
; Time: 14



@="C:\\Windows\\SysWOW64\\wpcumi.dll"


@="C:\\Windows\\System32\\wpcumi.dll"
====================================================
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.686
; File Description: DFA14C43-F385-4170-99CC-1B7765FA0E4A - aaa
; Date: 22.01.2010
; Time: 16



@="C:\\Windows\\SysWOW64\\wpcumi.dll"


@="C:\\Windows\\System32\\wpcumi.dll"
=====================================================
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.686
; File Description: jv16 PowerTools 2010 - Registry Cleaner
; Date: 22.01.2010
; Time: 16



@="C:\\Windows\\SysWOW64\\wpcumi.dll"


@="C:\\Windows\\System32\\wpcumi.dll"
=====================================================
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.686
; File Description: DFA14C43-F385-4170-99CC-1B7765FA0E4A - ccc
; Date: 22.01.2010
; Time: 19



@="C:\\Windows\\SysWow64\\wpcumi.dll"

@="C:\\Windows\\System32\\wpcumi.dll"

tullik

51. Registry Cleaner: when the initial results list contains certain detail lines, they often cannot be made to show in the Top Panel. (.) 644 x64

For some reason this rare incident, first reported in Beta 1, can be sort of reproduced if the situation described in the previous post exists.

Using the search word {DFA14C43-F385-4170-99CC-1B7765FA0E4A}\In, the list will contain only the four lines. Usually, no amount of mouse manipulation will make any of them show detail in the top panel.

I don't know if it will help, but here's a debug log.

*Top panel display issue.zip

curt

It would be nice to be able to clear the Statistics that jv16 PowerTools 2010 creates. To do this now I have to delete the Statistics.dat file from C:\Program Files\jv16 PowerTools 2010 Beta4\Settings. It would be nice to have a button in the jv16 PowerTools program that did this.

jv16

roberta wrote

I have been quietly evaluating each 2010 Beta including Beta 4.

And IMHO UNLESS a Major Sustained effort is put in Immediately, which seems unlikely looking at past history even for PT2010....

..it would be rather premature to issue a RC1 next (after the current Beta 4)....

You are correct, there is no need to rush it. So, after all the issues so far have been fixed, we'll release Beta 5.

ngc94227

Hi all!

I don´t know if it´s already mentioned before but If I use the directory tool I get the following: "Access violation in address 00750453 in module jv16PT.exe read of address 00000488

After I try to use the tool anyway it computes, says it´s done but could not access the directories I choose. So it has done anything...

Kind regards,

ngc94227

parkd1

When I run the unit testing tool I get an error. You can see the error in the rar file I have uploaded.

Unit Testing Tool.rar

parkd1

When I run the cleaner It does not fix or delete these. Why? Here is the rar file that shows them.

invalid file or directory reference.rar

tullik

Registry Cleaner - incorrect Open in RegEdit (on x64 Windows 7)

All instances described here are in the "Obsolete software entry" error type.

These keys are in the results list:
HKLM\Software\BigFix\

HKLM\Software\Gateway Incorporated\

HKLM\Software\Gateway\

The first two open at Computer with the left pane expanded at HKLM\Software. The BigFix and Gateway Incorporated keys do not exist in HKLM\Software.

The third one opens at HKLM\SOFTWARE\Gateway. A structure HKLM\SOFTWARE\Gateway\Metadata exists and has entries. This structure is not related to the error.

A "Custom registry backup" for the 3 keys in the list shows:

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.686
; File Description: **1 open in regedit wrong
; Date: 23.01.2010
; Time: 21

All those keys are empty and likely are what triggered the "Obsolete software entry" errors.

The results list needs to show the actual items causing errors. Showing nonexistent or unrelated items is simply not good at all!

141. Registry Cleaner: can show nonexistent or unrelated items instead of the items triggering the error detection. {.} 686 x64 w7

tullik

Registry Cleaner - top panel Ctrl+point+click (on x64 Windows 7)

When you do this operation on a folder that exists, the Explorer window opens on top and at that folder in the left pane.

When you do this operation on a folder that does not exist:

*** the Explorer window opens behind the other windows

*** the task bar flashes for attention to the Explorer window

*** the Explorer window opens at the user's personal folder

It would be better to just put out a message saying the folder does not exist.

Opening the Explorer window of the user's personal folder on top would be an acceptable compromise.

It would be best to open to the next prior folder in the path string that does exist, if any. If none at all exist, the message or the compromise would be done.

140. Registry Cleaner: top panel Ctrl+point+click at a nonexistent folder needs improvement. {.} 686 x64 w7

tullik

19. Software Uninstaller: on my systems, Custom Uninstall for “Netscape Navigator” always makes incorrect identifications under “Files” and “Advanced Settings.” IMO, it would be safer internally to ignore Netscape Navigator items, since the current algorithm associates them with Microsoft Office, Opera, and so forth. (.) 644 x64

If an inexperienced user were to click "Uninstall" for Netscape Navigator, I wonder what the program would think it needed to uninstall?

*01-24-2010_03-08-21.jpg

*01-24-2010_03-05-31.jpg

tullik

142. Software Uninstaller: access violation after closing Custom Uninstaller and just clicking a line in the main list. {.} 686 x64 w7

This occurs with some regularity if you did some deletes in the "Registry data" tab before closing Custom Uninstall.

*SW Uninstaller violation.zip

tullik

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.

tullik

jv16 wrote
roberta wrote

I have been quietly evaluating each 2010 Beta including Beta 4.

And IMHO UNLESS a Major Sustained effort is put in Immediately, which seems unlikely looking at past history even for PT2010....

..it would be rather premature to issue a RC1 next (after the current Beta 4)....

You are correct, there is no need to rush it. So, after all the issues so far have been fixed, we'll release Beta 5.

IMHO, the program would be ready for RC1 after these classes of bugs are seldom seen:

*** Backup and restore errors. Examples:
- 14. Backup tool: when restoring multiple backups at the same time, if some have the same description, some of those do not restore (per the messages). http://www.macecraft.com/phpBB3/viewtopic.php?p=22576#p22576
  
  144. Back up: it is possible that some Wow6432Node items are not backed up and therefore cannot be restored. See the red text at the end of this post: http://www.macecraft.com/phpBB3/viewtopic.php?p=22629#p22629
  
  See the red text at the end of this post: http://www.macecraft.com/phpBB3/viewtopic.php?p=22612#p22612
*** Errors at task or window switching points. Examples:
- Access violations
  
  Crashes
  
  Hangs
*** Windows APIs that very often do not respond correctly or at all when called on x64 systems. For example, these file or directory selection dialogues and some task invocations:
- Save list as ...
  
  Export as .reg file
  
  Save selected lines
  
  Explore
  
  Compare results...
  
  Font change dialogue
*** Often displaying incorrect registry keys in registry tool lists when Wow6432Node keys are involved. Examples:
- 48. Clean and fix my computer: the Registry junk group contains several “false positives,” or just bugs, for empty keys which exist under a Wow6432Node but show in the GUI as existing in green keys which actually don't exist.
  
  74. Registry Cleaner: some empty keys which do not exist in the registry are shown in green in the GUI, but the correct key exists under a Wow6432Node.
  
  141. Registry Cleaner: can show nonexistent or unrelated items instead of the items triggering the error detection.
  
  143. Software Uninstaller: Custom Uninstall GUI can point to non-Wow6432Node keys which don't exist when Wow6432Node keys are the correct ones.

tullik

Registry Cleaner (Reference mode)

The list shows HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs\ and C:\Windows\system32\mscomctl.ocx, both in green.

Of course, HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs\ does exist.

Unfortunately, C:\Windows\system32\mscomctl.ocx does not exist in the file system. It is also not an entry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs\.

It is an entry under HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDLLs. It still does not exist in the file system, but C:\Windows\SysWOW64\mscomctl.ocx does exist.

I don't know if we can call this a false positive. It's more like a double negative. Should I : or : ?

The list also shows HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDLLs\ and C:\Windows\system32\mscomctl.ocx, both in green. That item is half right, colorwise.

Using Reference mode, there are about 20 more "Invalid file or directory reference" items than in normal mode. I detail checked 3 more. They also are "double negatives" in exactly the same way.

Not only is PowerTools having trouble with things under Wow6432Node's, but it seems someone (MS?) put bad entries under ...\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDLLs.

Incidentally, I did a "Custom registry backup" of the two lines showing "mscomctl.ocx." If Delete would only remove what that shows, the backup would do a correct restore even with the minor error (entry duplication) in the backup Entries.reg.

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.686
; File Description: **3 C:\Windows\system32\mscomctl.ocx (bad SharedDLLs  entries)
; Date: 24.01.2010
; Time: 10



"C:\\Windows\\system32\\mscomctl.ocx"=dword

"C:\\Windows\\system32\\mscomctl.ocx"=dword

« Previous Page Next Page »