jv16 PowerTools 2010 Beta4 released!

[deleted]

tullik wrote
hukka wrote

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

{This always happens on my x86 Vista or x64 Windows 7 even when I delete SuperEasyFixIgnoreList.dat and rebuild it from scratch}

Unfortunately I was unable to reproduce this on x86 Windows 7 and x64 Vista.

Try to "Never show" some "MRU and History" items. The registry and file ignores do work.

I thought I had tested like that but apparently not - I can reproduce the bug now. Thanks.

tullik

@ hukka

hukka wrote
PowerTools 2010 Beta4 Bug Tracking

UNCONFIRMED ISSUES:

. . .

6. Opening a tool works but sometimes shows an Access Violation error message. This can also happen when closing a tool.

. . .

9. Directory Tool: right click->Properties gets an error pop-up from Windows. (x64)

. . .

16. Registry Cleaner: "Compare results" aborts itself every time. (x64)

. . .

19. Directory Tool: on x64 Windows 7, "Explore" does nothing at all. (x64)

20. File Tool: "Execute" does nothing. (x64)

Regarding #6:

it occurs only "sometimes" with several tools regardless of the OS or chip. On x86 Vista and x64 Windows 7, it occurs "every time" with Directory Finder.

Regarding #9, #16, #19, and #20:

under this heading and with the "(x64)" annotation, it reads like these do not occur with x64. Actually, they occur every time with my x64 Windows 7 and never with my x86 Vista. I don't have an x64 Vista system, but more testing would probably move these to the confirmed list with an annotation something like this: "(x64 only; x86 OK)"

[deleted]

tullik wrote
@ hukka

hukka wrote

UNCONFIRMED ISSUES:

. . .

6. Opening a tool works but sometimes shows an Access Violation error message. This can also happen when closing a tool.

. . .

9. Directory Tool: right click->Properties gets an error pop-up from Windows. (x64)

. . .

16. Registry Cleaner: "Compare results" aborts itself every time. (x64)

. . .

19. Directory Tool: on x64 Windows 7, "Explore" does nothing at all. (x64)

20. File Tool: "Execute" does nothing. (x64)

Regarding #6:

it occurs only "sometimes" with several tools regardless of the OS or chip. On x86 Vista and x64 Windows 7, it occurs "every time" with Directory Finder.

The Directory Finder AV is listed separately in Confirmed:

10. Directory Finder: Access Violation when clicking Start.

I haven't yet seen the random AVs happen otherwise except in the context of separately mentioned bugs, which is why I've left the issue as 'Uncorfirmed' thus far.

Regarding #9, #16, #19, and #20:

under this heading and with the "(x64)" annotation, it reads like these do not occur with x64. Actually, they occur every time with my x64 Windows 7 and never with my x86 Vista. I don't have an x64 Vista system, but more testing would probably move these to the confirmed list with an annotation something like this: "(x64 only; x86 OK)"

By "(x64)" I actually mean "x64 only; x86 OK" - I'll make a clarification. I can't access our x64 Windows 7 box, so x64 Vista is what I've used for testing.

tullik

hukka wrote
tullik wroteRegarding #6:

it occurs only "sometimes" with several tools regardless of the OS or chip. On x86 Vista and x64 Windows 7, it occurs "every time" with Directory Finder.

The Directory Finder AV is listed separately in Confirmed:

10. Directory Finder: Access Violation when clicking Start.

I haven't yet seen the random AVs happen otherwise except in the context of separately mentioned bugs, which is why I've left the issue as 'Uncorfirmed' thus far.

Yes, those start/close AV's are quite random and don't happen too often. Hopefully, the new debug log info jv16 put in Beta 4 will lead to fixes of specific AV problems and the random ones as well. There are about a dozen AV related debug logs already posted in the Beta 4 topic, so there will be something to look at.

Incidentally, the text for #6 Is probably not directly derived from a specific bug report, AFAIK. It is a fix description (#55) in the Beta 4 Release Notes.

hukka wrote
tullik wroteRegarding #9, #16, #19, and #20:

under this heading and with the "(x64)" annotation, it reads like these do not occur with x64. Actually, they occur every time with my x64 Windows 7 and never with my x86 Vista. I don't have an x64 Vista system, but more testing would probably move these to the confirmed list with an annotation something like this: "(x64 only; x86 OK)"

By "(x64)" I actually mean "x64 only; x86 OK" - I'll make a clarification. I can't access our x64 Windows 7 box, so x64 Vista is what I've used for testing.

If they don't occur with x64 Vista, I suppose they could be related just to x64 Windows 7.

Such things do exist. For example:

Subject: My vertical task bar won't stay the right size, that is, very thin.

I haven't observed the exact problems reported in this thread, but, as stated below, it involves task bar size. Even better, it's reproducible at will (on x64 Windows 7 Home Premium with latest Windows Updates).

.

.

.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

How do I report a Windows 7 bug that certainly exists?

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

I don't really expect an answer (unless there's a current solution). I just hope someone from MS logs the problem so it gets fixed later.

On up-to-date x64 Windows 7 Home Premium, this happens every time, as far as I can tell:

Configuration: task bar is on right side, auto-hidden, and locked. The width is about 2.5 inches.

The problem: the task bar width resets to a default size (about 0.75 inch) after "switch users" or after using "personalize" to pick a different theme. The workaround is easy: just unlock the task bar and drag it back to the desired size.

This doesn't happen with my x86 Windows 7 notebook with the same task bar configuration.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

I had to post this to a user forum since MS doesn't accept bug reports when their software is acquired via an OEM.

redseujac

Well, dear Hukka, I think the issues should be tested now on a Windows 7 64-bit system instead of on a Vista 64-bit system. Many jv16 PowerTools 2010 users will install the program on their new Windows 7 64-bit OS and not on an obsolete Vista 64-bit OS. I'm afraid you will not gain anything continuing testing on your Vista 64-bit machine :

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.

tullik

On x64 Windows 7

45. File Recovery Tool: results window shows no action buttons and the Top Panel and status bar are blank. _.._ 644 x64 |...| 686 x64 w7

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

86. File Recovery: at scan completion, the message window jumped up to the list's top panel. _.._ 678 x64 w7 |.| 686 x64 w7 Fixed or OTO

91. File Recovery: can get an access violation. If the scan is aborted, the violation can occur several minutes later. _.._ 678 x64 w7 |...| 686 x64 w7

122. File Recovery Tool: : The handle is invalid. {.} 686 x64 w7

The debug log reflects #46, #86, and part of #45 (no status line). I guess #86 is not fixed after all.

#91 and #122 are other "sometimes" things. Each has its own debug log, posted earlier in the topic (#91 is in the Beta 3 topic).

Sometimes the list looks OK but I've never seen the undelete work, even on x86 Vista. The log also shows # * * * * * Exception * * * * * Invalid class typecast after doing an undelete.

*File Recovery debug log.zip

*01-29-2010_13-07-07.jpg

tullik

On x64 Windows 7 in Vista SP2 compatibility mode

The Registry Compactor window came up. I wonder if it's safe to run the compaction?

tullik

149. Software Uninstaller: a redundant pop-up after 3rd party uninstaller ran; an incorrect concluding message. {.} 686 x64 w7

*01-29-2010_15-42-56.jpg

The CCleaner uninstall had already removed the folder. I had an Explorer window open for C:\Program Files (x86).

Messages:

: Starting software's uninstaller "C:\Program Files (x86)\CCleaner\uninst.exe" and waiting for it to run...

: Uninstaller ("C:\Program Files (x86)\CCleaner\uninst.exe") did not seem to run properly!

: All done! 0 B of data was removed (0 files, 0 directories, 0 registry entries and 0 registry keys).

Actually, it ran fine with no problems whatsoever.

*Uninstall debug log.zip

tullik

These column width issues were previously reported:

68. Backup Tool, Custom Restore: when switching between the Files and Registry tabs, the column widths are forgotten. _.._ 660 x86 Vista |...| 686 x64 w7

92. Desktop shortcuts: History Cleaner (for example) does not use the remembered column widths when started this way. _.._ 678 x64 w7 |...| 686 x64 w7

These column width and sort and window size issues are new in my testing log. Some have probably been reported earlier by other beta testers:

150. Registry Manager: when you browse through the tabs and change column widths, the changes are not remembered. {.} 686 x64 w7

151. Registry Finder: when you make the results window wider, the change is not remembered. The change is remembered when you make the window narrower. {.} 686 x64 w7

152. Registry Find & Replace: when you make the results window wider, the change is not remembered. The change is remembered when you make the window narrower. {.} 686 x64 w7

153. Registry Cleaner: when you make the results window wider, the change is not remembered. The change is remembered when you make the window narrower. {.} 686 x64 w7

154. Registry Monitor: when you make the results window wider, the change is not remembered. The change is remembered when you make the window narrower. {.} 686 x64 w7

155. Registry Monitor: when the tool abnormally terminates, the initial window's columns are reset to a very narrow width. {.} 686 x64 w7

156. File Tool: when files are first added, the initial column widths are calculated to an arbitrarily equal size. {.} 686 x64 w7

157. File Tool: when you change column widths, then add more files, the column widths are recalculated to an arbitrarily equal size. {.} 686 x64 w7

158. File Cleaner: the initial column widths are calculated to an arbitrarily equal size. {.} 686 x64 w7

159. Backup Tool: in a new session, the column sorts are a default, not the ones the user last did. {.} 686 x64 w7

pirateking

Loadout:

Windows 7 Home Premium 64 bit on Athlon 64 X2 dual core.

How to create fault:

* Select duplicate file finder.

* "Search in": select 4 directories from within the same parent directory.

* Files to find: "*.*".

* Start.

Fault:

JV16 stops working (activity wheel freezes) during the second phase - analysing. JV16 can be stopped by clicking the close icon and responding to the "stopped responding" dialogue box.

Repeatability:

Every time. It can be stopped by selecting 3 of the 4 directories (this removes 1000 of the 16000 or so files in the tree).

* STOP PRESS * I just ran it on a directory tree that I had previously scanned with Beta 3 successfully. A mere 6000 files and it hung.

Requests:

Could the analysing window have a summary of the amount of files found? The scanning window goes past so fast that I can't catch it.

Could the menu file in the duplicate display window have a "view containing directory" option as well as "list control" please? Sometimes it's helpful to view the duplicates in their context.

In the duplicate display window mouse scrolling moves by increments of entry - which isn't intuitive when the entry is expanded (the default). Could it move by visible line instead?

tullik

Beta 4 testing update:

New Beta 4 issues in tullik's testing log: 45

Prior issues confirmed as still present in Beta 4: 59

Beta 4 fixes and improvements which did not work (8, included in previous count)

Prior issues awaiting test in Beta 4 or later: 6

Beta 4 fixes and improvements not yet tested: 1

Issues confirmed to be OK in Beta 4: 146

Issues confirmed to be OK before Beta 4: 117

Total: 374

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Per the "big list", so far in the Betas, 263 issues and improvements have been confirmed to be OK as of now.

The 45 new issues I have seen in Beta 4 are listed at the end of the "big list": http://www.macecraft.com/phpBB3/viewtopic.php?p=22538#p22538

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

tullik

On x64 Windows 7 in Vista SP2 compatibility mode

The Unit Test tool stopped with this error: # Unit Testing - LOG: 1859 s. - Error: TestFileToolsEx : 5

*01-30-2010_04-18-17.jpg

Also, per the message window above, at the minute it stopped, it apparently got confused dealing with its own file.

*01-30-2010_04-35-05.jpg

*Unit test debug log.zip

160. Unit Testing tool: stopped with “Error: TestFileToolsEx : 5” 686 x64 w7 Vista mode

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.

tullik

For what it may be worth (maybe nothing), I'm running PowerTools 2010 on x64 Windows 7 in Vista SP2 compatibility mode for a while.

So far, the only significant difference I've noticed is the Registry Compactor window comes up.

tullik

On x64 Windows 7 in Vista SP2 compatibility mode

Unit Test Tool

My second try with this in compatibility mode almost ran to a successful end.

Here's the tool's log and a debug log.

0 s. - The tests will use C:\ for storing temporary data, testing access to the drive...


0 s. - ...The program has full access to C:\ drive!
0 s. - Testing Started...
42 s. - RDA Eff rate: 91.65%, FPO rate: 0.00%, FNE rate: 16.70%
81 s. - RDA Eff rate: 92.12%, FPO rate: 0.00%, FNE rate: 15.77%
114 s. - RDA Eff rate: 91.12%, FPO rate: 0.00%, FNE rate: 17.77%
150 s. - RDA Eff rate: 92.60%, FPO rate: 0.00%, FNE rate: 14.80%
150 s. - RegistryDataAnalyzer Test Done
162 s. - TSettingsManager Test Done
505 s. - FileTools Test Done
552 s. - StringToolsEx Test Done
553 s. - IsDangerousKey Test Done
601 s. - ExtractFilenameEx Test Done
753 s. - StringListFunctions Test Done
753 s. - TFileList Test Done
755 s. - Sorting Test Done
795 s. - Duplicate Finder Test Done
844 s. - TBackupTool Test Done
905 s. - TSafetyNet Test Done
929 s. - RNG Test Done
964 s. - StringTools Test Done
1004 s. - RDA Eff rate: 88.73%, FPO rate: 0.00%, FNE rate: 22.53%
1041 s. - RDA Eff rate: 91.58%, FPO rate: 0.00%, FNE rate: 16.83%
1084 s. - RDA Eff rate: 93.53%, FPO rate: 0.00%, FNE rate: 12.93%
1128 s. - RDA Eff rate: 96.53%, FPO rate: 0.00%, FNE rate: 6.93%
1128 s. - RegistryDataAnalyzer Test Done
1140 s. - TSettingsManager Test Done
1422 s. - FileTools Test Done
1449 s. - StringToolsEx Test Done
1450 s. - IsDangerousKey Test Done
1512 s. - ExtractFilenameEx Test Done
1681 s. - StringListFunctions Test Done
1681 s. - TFileList Test Done
1686 s. - Sorting Test Done
1730 s. - Duplicate Finder Test Done
1824 s. - TBackupTool Test Done
1908 s. - TSafetyNet Test Done
1916 s. - RNG Test Done
1927 s. - StringTools Test Done
1986 s. - RDA Eff rate: 91.53%, FPO rate: 0.00%, FNE rate: 16.93%
2034 s. - RDA Eff rate: 94.97%, FPO rate: 0.00%, FNE rate: 10.06%
2106 s. - Error: TestRDA: FPO rate of 0.10 is larger than accepted! : 1
2106 s. - RDA Eff rate: 95.48%, FPO rate: 0.10%, FNE rate: 8.93%
2157 s. - RDA Eff rate: 92.58%, FPO rate: 0.00%, FNE rate: 14.83%
2157 s. - RegistryDataAnalyzer Test Done
2169 s. - TSettingsManager Test Done
2380 s. - FileTools Test Done
2467 s. - StringToolsEx Test Done
2468 s. - IsDangerousKey Test Done
2582 s. - ExtractFilenameEx Test Done
2679 s. - StringListFunctions Test Done
2679 s. - TFileList Test Done
2681 s. - Sorting Test Done
2720 s. - Duplicate Finder Test Done
2785 s. - TBackupTool Test Done
2831 s. - TSafetyNet Test Done
2852 s. - RNG Test Done
2902 s. - StringTools Test Done
2974 s. - RDA Eff rate: 92.83%, FPO rate: 0.00%, FNE rate: 14.33%
3029 s. - RDA Eff rate: 94.05%, FPO rate: 0.00%, FNE rate: 11.90%
3029 s. - RegistryDataAnalyzer Test Done
3035 s. - TSettingsManager Test Done
3378 s. - FileTools Test Done
3453 s. - StringToolsEx Test Done
3454 s. - IsDangerousKey Test Done
3560 s. - ExtractFilenameEx Test Done
3767 s. - StringListFunctions Test Done
3767 s. - TFileList Test Done
3772 s. - Sorting Test Done
3798 s. - Duplicate Finder Test Done
3885 s. - TBackupTool Test Done
3980 s. - TSafetyNet Test Done
4001 s. - RNG Test Done
4022 s. - StringTools Test Done
4086 s. - RDA Eff rate: 93.12%, FPO rate: 0.00%, FNE rate: 13.77%
4158 s. - RDA Eff rate: 94.00%, FPO rate: 0.00%, FNE rate: 12.00%
4226 s. - RDA Eff rate: 90.05%, FPO rate: 0.00%, FNE rate: 19.90%
4310 s. - RDA Eff rate: 91.48%, FPO rate: 0.00%, FNE rate: 17.03%
4310 s. - RegistryDataAnalyzer Test Done
4317 s. - TSettingsManager Test Done
4599 s. - FileTools Test Done
4684 s. - StringToolsEx Test Done
4685 s. - IsDangerousKey Test Done
4803 s. - ExtractFilenameEx Test Done
5002 s. - StringListFunctions Test Done
5003 s. - TFileList Test Done
5007 s. - Sorting Test Done
5026 s. - Duplicate Finder Test Done
5073 s. - TBackupTool Test Done
5168 s. - TSafetyNet Test Done
5188 s. - RNG Test Done
5218 s. - StringTools Test Done
5218 s. - Error(s) : Error: TestRDA: FPO rate of 0.10 is larger than accepted! : 1

5218 s. - ...Testing Done!

*Unit Test debug log (2).zip

160. Unit Testing tool: stopped with “Error: TestFileToolsEx : 5” {.} 686 x64 w7 Vista mode

tullik

On x64 Windows 7 in Vista SP2 compatibility mode

Registry Compactor (It can be run on Windows 7. : )

There's a probable bug when doing a 49.9 MB Software hive. The program aborts for that hive only. Possibly it's just an error in the handling of numbers during a reasonableness check.

This is the message from the debug log: Registry Compact Aborted, DS=True, OldHiveSize=52346880, NewHiveSize=5234688

161. Registry Compactor: self-aborts before doing the compaction operation on a 49.9 MB SOFTWARE hive. The other hives compact OK. {.} 686 x64 w7 Vista mode

*01-30-2010_07-24-22.jpg

Note: the top part of the screenshot is probably a QuickShot.exe bug. The window did not look like that. That part of the window was the transparent title bar.

*Registry Compactor debug log.zip

tullik

In most lists, double clicking at a column margin to widen that column is not very reliable. Usually one gets an unwanted column sort.

This may well be caused by the "sort type" that inserts in the column header for debugging purposes. Hopefully, that will be taken out by RC1 at the latest.

tullik

95. Clean & fix my computer: access violation while creating a program backup using context menu. __ 678 x64 w7 |...| 686 x64 w7

More information:

It works with files.

It fails every time with registry entries.

After the AV, the window has a never-ending progress indicator.

You can close or abort the tool but the tool usually (always?) cannot be used successfully again until you close the current PT session.

*C&FMC AV in context backup.zip

tullik

25. Clean and Fix My Computer: there is a probable Wow6432Node issue involving PT2010 uninstall registry items, which cause an access violation and PowerTools hang when you try to “Export as a .reg file ' or “Save as a program backup.” __ 644 x64 (.) |..|

*** The list has 11 identical lines: HKLM\Soft\MSoft\Win\CurVer\uninstall\jv16 powertools 2010\, 99%, Obsolete Add / Remove menu entry

*** The top panel shows a key which does not exist in green: HKLM\Soft\MSoft\Win\CurVer\Uninstall\jv16 PowerTools 2010\

*** This key does exist: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\jv16 PowerTools 2010

*** I'll get a debug log and post it separately.

26. Registry Cleaner: also has a problem with the same 11 PT2010 uninstall registry items. Upon delete, it gets an access violation. However, the key and entries were deleted, the backup was correct for the Wow6432Node key (even though the list did not show that), and the program did not hang. I'll post a debug log separately. (I restored the backup and deleted three additional times, but the access violation did not recur – so no debug log is available. I'll post the Entries.reg file to the “Clean and Fix My Computer” post about its problem with the same items.) __ 644 x64 (.) |..|

These two are reproducible, for the most part, in Beta4 by merging this 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.644
; File Description: PT2010 install entries + Wow6432Node bug
; Date: 05.12.2009
; Time: 21



"Contact"="Macecraft Software Support Department"
"DisplayIcon"="\"C:\\Program Files\\Macecraft\\V\\Y-betas\\PT2010 pre-beta (vanilla install (5))\\Uninstall\\uninstall.exe\""
"DisplayName"="jv16 PowerTools 2010 Pre-Beta"
"DisplayVersion"=""
"HelpLink"="http://www.macecraft.com"
"Publisher"="Macecraft Software"
"UninstallString"="\"C:\\Program Files\\Macecraft\\V\\Y-betas\\PT2010 pre-beta (vanilla install (5))\\Uninstall\\uninstall.exe\" \"/U:\\Program Files\\Macecraft\\V\\Y-betas\\PT2010 pre-beta (vanilla install (5))\\Uninstall\\uninstall.xml\""
"URLInfoAbout"="http://www.macecraft.com"
"NoModify"=dword

"NoRepair"=dword

More information: in 686, the backup from C&FMC is incomplete and the backup from Registry Cleaner is strangely duplicated.

*C&FMC debug log.zip

« Previous Page Next Page »