jv16 PowerTools 2012 Beta2

arctucas

Regarding the History Cleaner:

I have noticed there are entries in Windows/System32/Log Files/WMI/RtBackup that the History Cleaner cannot delete, although manual deletion is possible.

And, before you ask, no, I did not have to change any permissions or ownership.

Therefore I also would say the History Cleaner is not working completely.

muggle

Windows Vista Ultimate_SP2 / 32

Pale Moon 8.0

Thank_U "Artucus" for taking the time to read my post... I was a little concerned that jv16 history cleaner was only being specific to my O/S personal settings & personal O/S adjustments. ...

and affecting my PC “only”...

I had reported this issue in the Beta1 forum and never received a response...?..

Now Beta2 History cleaner is performing and functioning in the same manner...

Only … M$ Paint & M$ Word Pad is cleaned by the History cleaner...

Does this mean my configuration settings in jv16 history cleaner are incorrect..?

It is with hope.. That the good people @ Jv16 can provide me with an answer...

DebugReport_18.12.2011.zip

jv16PT_debuglog.zip

again Thanks.. Artucus...

[deleted]

Leonardo wrote
Were you able to fix the XP-SP3 reported issue, "Settings -> Integration with windows" too?

Please see: http://www.macecraft.com/phpBB3/viewtopic.php?f=10&t=4603#p29765

Yes, this is now fixed too.

siliconman01

Sure would be nice to see Release Candidate 1 prior to Christmas weekend. ... :

john7

On my Dell running Dell Support Center/PC Checup keeps recreting entries under PC Tools which is what PC Checkup is from.

I had Dell support pind but somthging in the Beta removed the pining.

john7

Registry editer running very slow, as is 2011. Vista 32bit with two accoints/

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...

0 s. - SelfTest Done

1 s. - IsDangerousKey Test Done

15 s. - TSettingsManager Test Done

39 s. - ExtractFilenameEx Test Done

41 s. - Sorting Test Done

51 s. - RNG Test Done

56 s. - StringTools Test Done

56 s. - TFileList Test Done

84 s. - Duplicate Finder Test Done

130 s. - Error: TestTBackupManager : 22 SubID = 1 Par1 = HKEY_CLASSES_ROOT\*PT_UNIT_TEST Par2 = jv16PT_UnitTest_Data_777

131 s. - TBackupManager Test Done

137 s. - TSafetyNet Test Done

224 s. - StringListFunctions Test Done

235 s. - StringToolsEx Test Done

307 s. - RDA Eff rate: 87.56%, FPO rate: 0.00%, FNE rate: 24.90%

382 s. - RDA Eff rate: 89.76%, FPO rate: 0.00%, FNE rate: 20.50%

442 s. - RDA Eff rate: 87.48%, FPO rate: 0.00%, FNE rate: 25.05%

442 s. - RegistryDataAnalyzer Test Done

443 s. - SelfTest Done

444 s. - IsDangerousKey Test Done

463 s. - TSettingsManager Test Done

493 s. - ExtractFilenameEx Test Done

496 s. - Sorting Test Done

517 s. - RNG Test Done

529 s. - StringTools Test Done

529 s. - TFileList Test Done

544 s. - Duplicate Finder Test Done

596 s. - Error: TestTBackupManager : 22 SubID = 1 Par1 = HKEY_CLASSES_ROOT\*PT_UNIT_TEST Par2 = jv16PT_UnitTest_Data_777

596 s. - TBackupManager Test Done

602 s. - TSafetyNet Test Done

690 s. - StringListFunctions Test Done

700 s. - StringToolsEx Test Done

768 s. - RDA Eff rate: 87.38%, FPO rate: 0.00%, FNE rate: 25.25%

838 s. - RDA Eff rate: 89.51%, FPO rate: 0.00%, FNE rate: 21.00%

904 s. - RDA Eff rate: 88.13%, FPO rate: 0.00%, FNE rate: 23.75%

977 s. - RDA Eff rate: 87.63%, FPO rate: 0.00%, FNE rate: 24.75%

977 s. - RegistryDataAnalyzer Test Done

978 s. - SelfTest Done

979 s. - IsDangerousKey Test Done

1001 s. - TSettingsManager Test Done

1032 s. - ExtractFilenameEx Test Done

1035 s. - Sorting Test Done

1043 s. - RNG Test Done

1047 s. - StringTools Test Done

1047 s. - TFileList Test Done

1059 s. - Duplicate Finder Test Done

1159 s. - Error: TestTBackupManager : 22 SubID = 1 Par1 = HKEY_CLASSES_ROOT\*PT_UNIT_TEST Par2 = jv16PT_UnitTest_Data_777

1159 s. - TBackupManager Test Done

1172 s. - TSafetyNet Test Done

1296 s. - StringListFunctions Test Done

1299 s. - Error: TestStringToolsEx : 15 SubID = 0 Par1 = x Par2 = 5.10.9.336

1302 s. - StringToolsEx Test Done

1371 s. - RDA Eff rate: 87.61%, FPO rate: 0.00%, FNE rate: 24.80%

1442 s. - RDA Eff rate: 89.11%, FPO rate: 0.00%, FNE rate: 21.80%

1442 s. - RegistryDataAnalyzer Test Done

1443 s. - SelfTest Done

1443 s. - IsDangerousKey Test Done

1463 s. - TSettingsManager Test Done

1492 s. - ExtractFilenameEx Test Done

1494 s. - Sorting Test Done

1502 s. - RNG Test Done

1508 s. - StringTools Test Done

1508 s. - TFileList Test Done

1536 s. - Duplicate Finder Test Done

1568 s. - Error: TestTBackupManager : 22 SubID = 1 Par1 = HKEY_CLASSES_ROOT\*PT_UNIT_TEST Par2 = jv16PT_UnitTest_Data_777

1568 s. - TBackupManager Test Done

1578 s. - TSafetyNet Test Done

1713 s. - StringListFunctions Test Done

1733 s. - StringToolsEx Test Done

1799 s. - RDA Eff rate: 88.08%, FPO rate: 0.00%, FNE rate: 23.85%

1868 s. - RDA Eff rate: 88.33%, FPO rate: 0.00%, FNE rate: 23.35%

1972 s. - RDA Eff rate: 88.03%, FPO rate: 0.00%, FNE rate: 23.95%

1972 s. - RegistryDataAnalyzer Test Done

1973 s. - SelfTest Done

1973 s. - IsDangerousKey Test Done

1985 s. - TSettingsManager Test Done

2004 s. - ExtractFilenameEx Test Done

2007 s. - Sorting Test Done

2018 s. - RNG Test Done

2025 s. - StringTools Test Done

2025 s. - TFileList Test Done

2037 s. - Duplicate Finder Test Done

2082 s. - Error: TestTBackupManager : 22 SubID = 1 Par1 = HKEY_CLASSES_ROOT\*PT_UNIT_TEST Par2 = jv16PT_UnitTest_Data_777

2082 s. - TBackupManager Test Done

2086 s. - TSafetyNet Test Done

2223 s. - StringListFunctions Test Done

2228 s. - StringToolsEx Test Done

2295 s. - RDA Eff rate: 88.38%, FPO rate: 0.00%, FNE rate: 23.25%

2358 s. - RDA Eff rate: 88.31%, FPO rate: 0.00%, FNE rate: 23.40%

2421 s. - RDA Eff rate: 87.53%, FPO rate: 0.00%, FNE rate: 24.95%

2483 s. - RDA Eff rate: 86.46%, FPO rate: 0.00%, FNE rate: 27.10%

2483 s. - RegistryDataAnalyzer Test Done

2483 s. - Error(s) : Error: TestTBackupManager : 22 SubID = 1 Par1 = HKEY_CLASSES_ROOT\*PT_UNIT_TEST Par2 = jv16PT_UnitTest_Data_777

Error: TestTBackupManager : 22 SubID = 1 Par1 = HKEY_CLASSES_ROOT\*PT_UNIT_TEST Par2 = jv16PT_UnitTest_Data_777

Error: TestStringToolsEx : 15 SubID = 0 Par1 = x Par2 = 5.10.9.336

Error: TestTBackupManager : 22 SubID = 1 Par1 = HKEY_CLASSES_ROOT\*PT_UNIT_TEST Par2 = jv16PT_UnitTest_Data_777

2483 s. - ...Testing Done!ista 32bit registry tool running very slow

vasek

John7 wrote
Registry editer running very slow, as is 2011. Vista 32bit with two accoints/

32bit registry tool running very slow

What is exactly slow? Steps to reproduction please... Registry Editor does not exist in PowerTools. Registry tool running without problems under Vista SP2 32bit with two accounts.

john7

It was taking about one minute for each entry being corrected, they were displayed at bottom of window. I have had this since 2011 version, using 2010 has no problems. The initial build of 2011 needed a hard reboot to get it closed as it wasn’t doing anything even after 30-40 minutes. The last builds of 2011 had the same very slow correction of errors in the beta and as both do now allow aborting (sometimes leading to an error log displaced (after it closes) but usually not now (this was sent a long time ago to support))

I’m sorry I have no idea what “Registry Editor does not exist in PowerTools” is about?

Reproduce, run registry cleener which works OK then select what to be fixes and fix then goes very very slow'.

vasek

John7 wrote

Reproduce, run registry cleener which works OK then select what to be fixes and fix then goes very very slow'.

It is probably something wrong with your installation of PowerTools or with your PC. On Vista SP2 32bit (on XP and 7 also) no problems...

A Debug log please... How make the Debug Log? See the first post.

vasek

Cannot delete a disabled item in the Startup Manager. See jv16PT_debuglog_Startup Manager.html

Steps to reproduction:

1. Run Startup Manager

2. Select an item, click on the button Disable

3. Select the same item, click on the button Delete

4. Run msconfig (Win+R, write "msconfig") - the item is not deleted

john7

Hi will have a go when more time as a bit hetic whih chrismass at pressemt!

Reagrds

John

bgreen.andover

Power Tools 2012 Beta 2 reported 40 "software deep trace" items but reported "Failed to modify . . ." when fix was selected.

Windows Vista Home Premium SP2, AMD Athlon 64x2 Dual Core 4400+; 2.3 GHz; 3.5 GB RAM; 32 bit system

Same Result after rebooting.

john7

Vasek wrote
John7 wrote

Reproduce, run registry cleener which works OK then select what to be fixes and fix then goes very very slow'.

It is probably something wrong with your installation of PowerTools or with your PC. On Vista SP2 32bit (on XP and 7 also) no problems...

A Debug log please... How make the Debug Log? See the first post.

Well for some totally unknown reason it worked OK this time! I got it to fix over 1000 errors in of different sorts and it went ahead and did it. Which was a good thing as I was unable to find anything saying to save a debug log? I was also able to restore all the deletions made. I haven’t had time to try 2011 to see if that also is now working, will do that by restoring something from that another day.

There have been no updates or changes OTHER than I disabled power saving to run the test I just reimbursed! Its that the rerun was again very very slow. No idea where to get a bug report however as can’t see save it!

I have a NIVIDA 9500GT card using Vista power saving setup for display 15 minutes , computer 30 minutes. I changed this to 20 minutes and 3hrs befor doing the successful test and back for the second one that worked very slowly again.

I also found the deep trace bug was present, the entriesd found were the only ones not fixed.

vasek

bgreen.andover wrote
Power Tools 2012 Beta 2 reported 40 "software deep trace" items but reported "Failed to modify . . ." when fix was selected.

Windows Vista Home Premium SP2, AMD Athlon 64x2 Dual Core 4400+; 2.3 GHz; 3.5 GB RAM; 32 bit system

Same Result after rebooting.

Confirmed on the same system. See jv16PT_debuglog_deeptraces.html

leonardo

John7 wrote
........Well for some totally unknown reason it(beta2) worked OK this time! I got it to fix over 1000 errors off different sorts and it went ahead and did it. Which was a good thing as I was unable to find anything saying to save a debug log? I was also able to restore all the deletions made. I haven’t had time to try 2011 (again) to see if that also is now working, will do that by restoring something from that another day.

There have been no updates or changes OTHER than I disabled power saving to run the test I just reimbursed!

Its that the rerun was again very very slow. No idea where to get a bug report however as can’t see save it!

I have a NIVIDA 9500GT card using Vista power saving setup for display 15 minutes , computer 30 minutes.

I changed this to 20 minutes and 3hrs befor doing the successful test and back for the second one that worked very slowly again.

I also found the 'deep trace bug' was present, the entries found were the only ones not fixed........

Could it be related to installed drivers? Are you at the latest update levels for the Dell, Vista/32bit and NIVIDA 9500GT drivers?

john7

Yes, few motherboard or video updats now as rather old. Changes to the latter have been games related for a long time but have installed them mnow and then. Vista is updated on update Tusday every month! But video was updated via a MS update some months ago.

No pronlems with Dell laptop or a HP one both using ATI video chips, the former intell board drivers the latter AMD.

There have been no isues with 2010, 2011 was totally usless when first out and needed a hard rebpoot to get rid off. Now with 2011 and 2012 abort work and with powere saving changed 2011 will run slow and 2012 runs OK.

redseujac

1) Memory

Sometimes after closing the program the 'jv16PT.exe *32' process remains in memory. In Task Manager I have to end the process manually.

It happens e.g. when I open 'Remove on Reboot' from the Main window > 'File Tools' and then close the program again.

2) File Tools

The following issue applies to the tools 'Merge files', 'Split files', 'Remove on reboot', 'Mass Rename', 'Find an replace inside files', 'Wipe files'. When I open those tools from the Main window > File Tools, and I click on the 'Close' button, jv16 PowerTools is closed entirely, while IMHO the user should be redirected to the initial window 'File Tools'. When I click on the in the upper right corner, I return to the intitial window properly.

3) File Recovery

'Files to find': *.* - 'Search in': C:\

When I click 'Start', I get 'The following infomation must be provided: correct size search settings or uncheck the option'.

The option to search by size IS unchecked.

So the tool does not work.

4) Registry Monitor

Created simple snapshot (default settings).

When I try to compare it with actual registry, it fails.

The 'hourglass' keeps spinning, but nothing happens.

jv16PT.exe process takes huge memory nearly 198.000 kB.

vasek

redseujac wrote
1) Memory

Sometimes after closing the program the 'jv16PT.exe *32' process remains in memory. In Task Manager I have to end the process manually.

It happens e.g. when I open 'Remove on Reboot' from the Main window > 'File Tools' and then close the program again.

2) File Tools

The following issue applies to the tools 'Merge files', 'Split files', 'Remove on reboot', 'Mass Rename', 'Find an replace inside files', 'Wipe files'. When I open those tools from the Main window > File Tools, and I click on the 'Close' button, jv16 PowerTools is closed entirely, while IMHO the user should be redirected to the initial window 'File Tools'. When I click on the in the upper right corner, I return to the intitial window properly.

These issues are already reported - see this post - thank you for confirmed.

redseujac wrote
3) File Recovery

'Files to find': *.* - 'Search in': C:\

When I click 'Start', I get 'The following infomation must be provided: correct size search settings or uncheck the option'.

The option to search by size IS unchecked.

So the tool does not work.

Not confirmed.

redseujac wrote
4) Registry Monitor

Created simple snapshot (default settings).

When I try to compare it with actual registry, nothing happens.

The 'hourglass' keeps spinning, but nothing happens.

jv16PT.exe process takes huge memory nearly 198.000 kB.

Not confirmed on Vista SP2 32b. Debug Log please...

vasek

"jv16PT.exe" process remains in memory after huge searching (default settings, search in C:\) in the File recovery tool. See jv16PT_debuglog_memory.html.

leonardo

redseujac wrote

3) File Recovery

'Files to find': *.* - 'Search in': C:\

When I click 'Start', I get 'The following infomation must be provided: correct size search settings or uncheck the option'.

The option to search by size IS unchecked.

So the tool does not work.

4) Registry Monitor

Created simple snapshot (default settings).

When I try to compare it with actual registry, it fails.

The 'hourglass' keeps spinning, but nothing happens.

jv16PT.exe process takes huge memory nearly 198.000 kB.

3. Not confirmed for XP-SP3 and W7-SP1 x86

4. Not confirmed for XP-SP3 and W7-SP1 x86

Could other W7-SP1 64bit users please test the above mentioned issues 3). and 4).

« Previous Page Next Page »