jv16 PowerTools 2013 Beta2

jv16

Leonardo wrote
W7-x64 with jv16PT2013 Beta2.

Decrap function:

Please see: http://www.macecraft.com/phpBB3/viewtopic.php?f=10&t=4806#p31299 for previous test information.

1. The Decrap uninstall/cleanup function does not seem to function effectively.

After the 'confirmed' deinstallation of Java 7 update-9 and Java 7 update-10 I tried to do a clean Java 7 Update-10 reinstall.

However the Java Setup Utility came with an error code 1714 "a previous version of Java 7 update 10 could not be uninstalled.

Am I wrong to expect that that was what Decrap uninstall was supposed to do?

Using Registry Finder I deleted several old java registry items but so far it did not solve the problem, error code 1714 keeps coming back.

There seems to be something that is not removed during the uninstallation. This is quite normal for very complex software like Java, and especially when removing it just partially (i.e. removing a Java Update, not the entire Java).

Leonardo wrote

Decrap_Java 7 upd10 install problem.jpg

2. If I deselect ALL found items in Decrap Step 1 (so nothing to do!) and click 'Next', I expected a message 'Please select at least one item' but Decrap just continued:

a. Taking a System Restore point,

b. Step 3 select the 'Uninstallation options', after choosing 'Manual' and 'Clean the registry but let me verify the results'

c. Step 4, the uninstall, did not run because no items were selected in Step 1.

d. Warning message pops up. Clicking 'Yes' starts Step 5 the Registry cleaning.

e. At the display of the Scan result list, click 'Next' and this will show (only after a clean start of beta 2!) the window 'Please wait, finalizing the System restore point'.

f. This screen stay's on forever till you click 'Next' which does finish Decrap. However I doubt if the 'Registry Cleaning' is actually completely executed!!

g. If I repeat the actions from Point 2a thru 2e, now 112 items! are shown in the Registry scan result list.

Issue confirmed and fixed, thank you for reporting! The fix in question will be included to the next released version.

jv16

tullik wrote
Version 2.1.0.1236 (Beta 2) on 32-bit Windows 7

Backup Tool:

Custom restore/Edit backup should not be an option for an "Automated task" type backup.

Only a full restore will work for an automated task. Editing of a restored task is best done with the Automation Tool.

Agreed and done. Thank you for the idea!

jv16

tullik wrote
Version 2.1.0.1236 (Beta 2) on 32-bit Windows 7

Main window message area:

About once a day, a cosmetic overlap occurs when starting PowerTools.

This should now be fixed. I say should be, since I cannot reproduce the problem at will, so I cannot confirm the fix. I think I have also sometimes seen this problem, though. Thank you for reporting!

jv16

Leonardo wrote
Unit Testing Tool:

Is there still a need to run jv16PT2013-Beta2 'Unit Testing tool' using W7-x64 SP1?

.

No need (for you or anyone else) to use the Unit Testing Tool for the Beta 2. Please go ahead and give it a try with the next beta build (beta 3).

jv16

tullik wrote
Version 2.1.0.1236 (Beta 2) on 32-bit Windows 7

Changes from Beta1:

Not fixed:

Bug fix: The Backup tool can take seconds to open.

The first start of the tool took 40 seconds to load the Registry backups list.

Switching to the File backups list took 24 seconds for it to show.

Switching back to the Registry backups list took 25 seconds for it to show.

Times are approximate. The debug log is for a repeat of the above tests plus a switch to the Other backups list.

Backup tool list switching.zip

This is now fixed, not once but twice. There were actually two issues:

1) Sometimes the backup system would create an incomplete backup structure (e.g. during an aborted operation), which was not properly removed.

2) Loading the list of backups can in some cases take a long time.

Both of these issues should now be fixed, these fixes will be included in the upcoming Beta3.

tullik

jv16 wrote
tullik wroteVersion 2.1.0.1236 (Beta 2) on 32-bit Windows 7

Main window message area:

About once a day, a cosmetic overlap occurs when starting PowerTools.

This should now be fixed. I say should be, since I cannot reproduce the problem at will, so I cannot confirm the fix. I think I have also sometimes seen this problem, though. Thank you for reporting!

You can reproduce it at will. Before starting PowerTools, just remove the red line from ...\Settings\misc.dat each time you want to see it.

RestartPT=False

SysAccess=41294

Tutorial=False

tullik

Version 2.1.0.1236 (Beta 2) on 32-bit Windows 7

...

tullik wrote
Version 2.1.0.1235 (Beta 1) on 32-bit Windows 7

Registry Cleaner:

The program does not remember manual resizing of the Tool window.

The program does not remember manual resizing of the results window.

tullik wrote
Version 2.1.0.1235 (Beta 1) on 32-bit Windows 7

History Cleaner: the program does not remember manual resizing of the List Data window. It does remember when a full screen window was the last one used.

This issue exists for most tool and results list windows.

I did some testing noting changes the program made to ...\Settings\Windows.dat.

It seems the program does remember the manual resizing. Unfortunately, it does not use what it remembered when the windows are loaded again.

tullik

tullik wrote
Can File Finder Columns...Date... also say "all" so one does not have to go there three times to see all three dates?

jv16 wrote
That would indeed be quite nice, however it would require rather large improvements to the search routines. Therefore I'd rather not do such large scale changes at this point of development.

I have moved this topic to Feature Requests from where I (hopefully) notice it when working on the next major update.

tullik wrote
Sounds good.

tullik

Version 2.1.0.1236 (Beta 2) on 32-bit Windows 7

Program Debug Tool (a few anomalies):

Testing Report of jv16 PowerTools 2013

Features Tested
- Buttons: 202 / 215
  
  Windows: 66 / 66
  
  Overall Progress: 95.37%
  
  Hash: 89AD896C761B788C73D19F7D2329ADC9
Features Not Tested (13 Abort buttons)
- Clean and Fix My Computer results window : Button: Abort3 (high volume test may be necessary for this)
  
  Decrap Tool : Button: Abort (???)
  
  File Find and Replace results window : Button: Abort2 (high volume test may be necessary for this)
  
  File Tool : Button: Abort3 (???)
  
  File Tool : Button: Abort (??? - with >43,000 files in the list, no Abort button was visible with use of Select inverse many times)
  
  File Tool : Button: Abort6 (???)
  
  License download tool : Button: Abort (button may be pointless due to speed of the feature)
  
  License Information Tool : Button: Abort (button may be pointless due to speed of the feature)
  
  Multi input window : Button: Abort (high volume test may be necessary for this)
  
  Registry Cleaner results window : Button: Abort2 (high volume test may be necessary for this)
  
  Registry Monitor : Button: Abort (high volume test may be necessary for this)
  
  Software Uninstaller : Button: Abort (high volume test may be necessary for this)
  
  Start Menu Tool results window : Button: Abort (button not working, or pointless)

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

There is at least one issue with the Abort button in the Backup Tool.

It does not "depress" like a button when clicked.

It does not cause an Abort when clicked.

It is not recognized as a button by the Program Debug Tool. Proof? Rename DebugTool.dat before starting PT2013; then start PT2013 and run the Program Debug Tool first thing. The Debug Report will show no buttons have been clicked, and there is no Backup Tool Abort button listed in the report. There is possibly a spelling discrepancy somewhere.

There seem to be some "orphans" in DebugTool.dat. My Debug Report shows 13 unclicked abort buttons, but my DebugTool.dat file has 31 lines with formname.buttonname=0. They are:

backuptoolform.abortbtn=0
cleanandfixform2.abortbtn=0
cleanandfixform2.abortbtn3=0
custrestoreform.abortbtn=0
decrapform.abortbtn2=0
fileencryptform.abortbtn=0
fileviewform.abortbtn3=0
fileviewform.abortbtn5=0
fileviewform.abortbtn6=0
findreplaceform2.abortbtn2=0
ignorelisteditorform.abortbtn=0
internetupdateform.abortbtn=0
internetupdateform.btnbuy=0
internetupdateform.btndownload=0
licensedownloadform.abortbtn2=0
licensetoolform.abortbtn=0
licensetoolform.buylicbtn=0
multiinputform.abortbtn=0
multiinputform.button1=0
regcleanerform.button1=0
regcleanerresultsform.abortbtn3=0
regcleanerresultsform.button1=0
regcleanerresultsform.button3=0
regmonitorform.abortbtn=0
servicemanagerform.removebtn=0
softwareuninstallerform.abortbtn2=0
softwareuninstallerform.button1=0
softwareuninstallerform.button2=0
softwareuninstallerform.button3=0
startmenufixerform2.abortbtn=0
tutorialform.backbtn=0

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.

leonardo

W7-x64 with Version 2.1.0.1236 (Beta 2)

'Main menu' -> 'Tools' -> 'Program Maintenance' -> execute 'Reset Statistics'.

The Statistics on the bottom part of the 'Main menu' are not updated until a jv16PT-2013-Beta2 restart, this is not consistent with previous jv16PT versions.

Issue is 100% repeatable on both my laptop and desktop.

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.

jv16

tullik wrote

Actually, it's just a matter of timing. When a PT session starts, if a bugreport.txt exists, the crash or crashes logged in it are placed nicely in the debug log. The crash or crashes occurred in a single prior session. If the just started session gets a new crash, a new bugreport.txt reflects that, but it won't be in a debug log until the next session.

"Such a Debug Log" is posted here: http://www.macecraft.com/phpBB3/viewtopic.php?p=31333#p31333

You are correct, this issue is now fixed. Thank you for reporting! The fix will be included to the next released version.

jv16

tullik wrote
Version 2.1.0.1236 (Beta 2) on 32-bit Windows 7

Registry Finder:

"Ignore word" hits in "value data" occur even when "Analyze value data" is not a selected option.

This is by design, the "analyze value data" option refers to the search feature, the Ignore Words are always checked against all the possible data.

jv16

tullik wrote
jv16 wrote
tullik wroteVersion 2.1.0.1236 (Beta 2) on 32-bit Windows 7

Main window message area:

About once a day, a cosmetic overlap occurs when starting PowerTools.

This should now be fixed. I say should be, since I cannot reproduce the problem at will, so I cannot confirm the fix. I think I have also sometimes seen this problem, though. Thank you for reporting!

You can reproduce it at will. Before starting PowerTools, just remove the red line from ...\Settings\misc.dat each time you want to see it.

RestartPT=False

SysAccess=41294

Tutorial=False

Thank you for the tip! With this line removed, the problem does not occur with the fixed version.

We are still doing some fine tuning with the registry cleaner engine, the new beta version should be ready within a few days.

jv16

tullik wrote
tullik wroteCan File Finder Columns...Date... also say "all" so one does not have to go there three times to see all three dates?

jv16 wrote
That would indeed be quite nice, however it would require rather large improvements to the search routines. Therefore I'd rather not do such large scale changes at this point of development.

I have moved this topic to Feature Requests from where I (hopefully) notice it when working on the next major update.

tullik wrote
Sounds good.

Feature now added, thank you for reminding me!

jv16

Leonardo wrote
W7-x64 with Version 2.1.0.1236 (Beta 2)

'Main menu' -> 'Tools' -> 'Program Maintenance' -> execute 'Reset Statistics'.

The Statistics on the bottom part of the 'Main menu' are not updated until a jv16PT-2013-Beta2 restart, this is not consistent with previous jv16PT versions.

Issue is 100% repeatable on both my laptop and desktop.

Issue confirmed and fixed, thank you for reporting! This fix will be included to the next released version!

thomas-k

I use jv16 PowerTools on a Windows XP SP3 system. I miss the desktop program symbol.

jv16

thomas-k wrote
I use jv16 PowerTools on a Windows XP SP3 system. I miss the desktop program symbol.

I'm afraid I don't quite understand, what is missing?

thomas-k

jv16 wrote
thomas-k wroteI use jv16 PowerTools on a Windows XP SP3 system. I miss the desktop program symbol.

I'm afraid I don't quite understand, what is missing?

The program jv16 PowerTools has no icons.

icon.png

« Previous Page Next Page »