jv16 PowerTools 2009 Beta3 released

jv16

Here is the Beta 3 of jv16 PowerTools 2009:

http://www.macecraft.com/downloads/betas/jv16pt_setup_2009_beta3.exe

(If the link doesn't work it means the testing for this version has already ended)

Warning:

Do not install this beta version over any existing version but to a new directory. Also, do not uninstall any previous versions of jv16 PowerTools before the installation of this version - this version is a beta version. Beta version means the new product version is not yet finished and is only released for testing purposes in order to find the last remaining problems.

Do not start to translate this version to your language yet, there will be more changes to the language interface.

Main changes since Beta 2:

* All the graphics are now final (Unless you dear beta testers find something still to improve)

* Fixed a bug from the File Tool's Copy feature, it copied all the files not once but five times

* Fixed three bugs from the Automation Tool that made some of its feature not to work

* Fixed a bug that caused the Custom Fixing feature of the Registry Cleaner not to fix the data correctly

* Fixed a handful of bugs from the System Optimizer

* Fixed a problem that caused all the products to be minimized if you attempted to minimize only one

* Added System Optimizer to the main window's Tools menu and added support for the -SystemOptimizer command line parameter

* Added a hint to System Optimizer to tell the user how to undo the made changes

* Fixed a bug that caused the Right-Click menu of the Registry Cleaner not to open

* Added the Custom Fix feature back to Registry Cleaner (feature was disabled in previous betas)

* Fixed a few typos and some bad English

* Fixed a bug that could occur if some of the product's own files were protected against writing with the Read Only file attribute

* Added support to "File > Save list as" feature back to the new Registry Cleaner

* Fixed a typo from the About window

* Fixed a few GUI problems from the License Tool and Mass File Rename tool

* Fixed a bug from the Registry Compactor that caused certain registry hives not being listed on some systems

Release notes:

* The new and improved Scan Report is not available yet.

* The Mouse Gestures do not yet work perfectly.

As always, all beta testers who give us valuable feedback such as good quality bug reports or other feedback will be given a free personal license for the product when then final product version is released. To be clear, simply downloading the beta version and saying "it works fine" or "it doesn't work" doesn't entitle for a free license.

Please send all your comments and bug reports to this thread (using Post Reply button).

siliconman01

Vista SP1 Business 64-bit with dual drives. The second harddrive (E: & F:) is a clone of my primary harddrive (C: & D:)

The Registry Compactor is showing all Hives. HOWEVER, 6 of the hives shown are from my E: drive instead of from the C: drive.

Also the Registry Info is not showing all the hives.

siliconman01

As posted for Beta2, the Startup Manager is not showing all the startup programs.

jv16

siliconman01 wrote

Also the Registry Info is not showing all the hives.

What do you mean exactly?

siliconman01

jv16 wrote
siliconman01 wrote

Also the Registry Info is not showing all the hives.

What do you mean exactly?

In the pic for Registry Info, it is showing a total registry size of 22.7 mb and only 5 hives. Compare this to the pic of Registry Compactor list of hives.

ALSO, the Registry Cleaner is not scanning all the hives in Beta3. It only scans about 650000 keys and values. Under Vista 32-bit, the keys and values were over 1200000.

jv16

siliconman01 wrote

In the pic for Registry Info, it is showing a total registry size of 22.7 mb and only 5 hives. Compare this to the pic of Registry Compactor list of hives.

The Registry Compactor analyzes the registry on file system level, this means that the hives it lists are the actual storage files of the registry, i.e. the way the registry data is saved to the hard disk. There number of these storage files is not linked to the root keys fo the registry analyzed by the Registry Information tool. Hence also the different terms, "hives" and "root keys".

The same applies to the size difference. The Registry Info tool shows how much data the registry contains, the Registry Compactor shows how much space it takes from the system to store this data in disk. So the latter figure contains also all the structural information and metadata, but also the data can be compressed.

ALSO, the Registry Cleaner is now not scanning all the hives in Beta3. It only scans about 650000 keys and values, whereas PT 2008 scans over 1200000 keys and values.

There's something about this in the PT's handbook (FAQ section) but basically the numbers are shown merely to show progress, not to be used as comparison. For example, the Registry Cleaner counts every time it analyzes a piece of data, so debending on the engine version some data can be analyzed by just one analyzer module or three modules, and since each module increases the analyzed number there can be huge differences between versions and especially between different products.

jv16

siliconman01 wrote
Vista SP1 Business 64-bit with dual drives. The second harddrive (E: & F:) is a clone of my primary harddrive (C: & D:)

The Registry Compactor is showing all Hives. HOWEVER, 6 of the hives shown are from my E: drive instead of from the C: drive.

Does these paths from the wrong disk drives also exist in the right drive? So for example, does C:\Windows\System32\config\SAM exist?

siliconman01

Okay... I accept your explanation on the Reg Info and Reg Scanner. :)

siliconman01

jv16 wrote
siliconman01 wroteVista SP1 Business 64-bit with dual drives. The second harddrive (E: & F:) is a clone of my primary harddrive (C: & D:)

The Registry Compactor is showing all Hives. HOWEVER, 6 of the hives shown are from my E: drive instead of from the C: drive.

Does these paths from the wrong disk drives also exist in the right drive? So for example, does C:\Windows\System32\config\SAM exist?

Yes, see pic below from my C drive

jv16

siliconman01 wrote
jv16 wrote
siliconman01 wroteVista SP1 Business 64-bit with dual drives. The second harddrive (E: & F:) is a clone of my primary harddrive (C: & D:)

The Registry Compactor is showing all Hives. HOWEVER, 6 of the hives shown are from my E: drive instead of from the C: drive.

Does these paths from the wrong disk drives also exist in the right drive? So for example, does C:\Windows\System32\config\SAM exist?

Yes, see pic below from my C drive

Very strange... Could you try whether it makes any difference if you start the PowerTools using Right-Click > Run as administrator?

siliconman01

jv16 wrote

Very strange... Could you try whether it makes any difference if you start the PowerTools using Right-Click > Run as administrator?

Run as Administrator shows the same e: drive entries.

siliconman01

If I disable my E drive via BIOS, Reg Compactor shows this:

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.

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.

jv16

redseujac wrote
"Force Windows core to RAM" was/is checked.

I unckecked it and pressed "Apply" ... Followed the messages below:
 Internal Error: Backup file doesn't exist "C:\Program Files\jv16 PowerTools 2009B3\Backups\SystemOptimizer\1-7\index.dat"!
 Done!
 Please restart your computer for the changes to take effect
After rebooting I noticed no changes have been made to the registry entry, the tweak was still checked and no backup has been made.

Did you uninstall previous beta version before installing the Beta3? And had you used the System Optimizer with Beta2 to enable the "Force Windows core to RAM" tweak?

If so, the effect is very logical - it wasn't possible to undo the tweak because the backup file was missing (due to uninstall before updating to latest version).

tullik

PT2009 beta3 -- regarding apparently fully fixed items from the prior betas

The issues below appear to be fixed in beta3:

PT windows, minimizing any one minimizes all of them. . . . . . . . . . . . . . . . Fixed in PT2009 beta3 . . . . . . (1)

Main window tools menu, System Optimizer is missing . . . . . . . . . . . . . . . . Fixed in PT2009 beta3 . . . . . . (1)

System Optimizer, command line missing. . . . . . . . . . . . . . . . . . . . . . . . . Fixed in PT2009 beta3 . . . . . . (1)

Registry Cleaner, no line context menu with structured list. . . . . . . . . . . . . . Fixed in PT2009 beta3 . . . . . . (1)

File Finder, two bugs in "Search by owner" feature . . . . . . . . . . . . . . . . . . . Fixed in PT2009 beta3 . . . . . . (1)

File tools, "Copy to …" feature makes multiple copies, not just one . . . . . . . . Fixed in PT2009 beta3 . . . . . . (1)

Registry Cleaner, Custom Fix, doesn't fix and adds a bad entry name. . . . . . . Fixed in PT2009 beta3 . . . . . . (1) (2)

List Filter, bug with "hidden" part of list. . . . . . . . . . . . . . . . . . . . . . . . . . Fixed in PT2009 beta3 . . . . . . (1)

tullik

PT2009 beta3 -- regarding not fully fixed items from the prior betas

Automation Tool, allows user-pasted invalid characters in jvb filename . . . . . Mostly fixed in PT2009 beta3 . . . (1)

The colon character in a paste action still causes the internal error 9941.

For example, this paste (Delete Files with the File Cleaner a\a/a*a?a"a<a>a|b) causes the error.

Another paste (Delete Files with the file Cleaner a\a/a*acolona?a"a<a>a|b) results correctly in this filename: Delete Files with the file Cleaner aaaacolonaaaaab.jvb, so of the 9 invalid characters, only the colon is missed.

Automation tool, three defined actions do not work . . . . . . . . . . . . . . . . . . Partly fixed in PT2009 beta3 . . . (1)

The History Cleaner function works now. The two "Delete files from directories" functions still do not delete anything. Additionally, their jv16PT.exe processes remain active and have to be killed to make them go away. These are their jvbs:

<RemoveFiles> C:\Temp\ C:\Users\Owner\AppData\Local\Temp\ C:\Windows\Temp\
<Terminate>

<RemoveFilesWithSubs> C:\Temp\ C:\Users\Owner\AppData\Local\Temp\ C:\Windows\Temp\ 
<Terminate>

Service Manager, window resize not remembered. . . . . . . . . . . . . . . . . . . . Not fixed in PT2009 beta3 . . . . (1)

As before, it remembers the window resizing within the same PT2009 session, but has forgotten when you start PT2009 anew.

Message box, widening a window can produce garbled text in the box. . . . . . . Not fixed in PT2009 beta3 . . . . (1)

As before, widening a window which has a Tip in its message box can produce garbled text in the right side of the message box.

System Optimizer, unreliable "undo" due to backup & apply bugs . . . . . . . . . . Not fixed in PT2009 beta3 . . . . (1)

According to redseujac, this new tool still has some issues. After I back up the registry and restart, I'll do a few tests and post the findings in another post.

tullik

PT2009 beta3 -- regarding an item not reported in the prior betas

Automation Tool:

* The Delete Files with the File Cleaner feature, set to List all files from the computer's temp directories, shows no window (and deletes nothing). The jv16PT.exe process, after using cpu, sits at cpu 0 in Task Manager and has to be killed to make it go away.This is the jvb:

<FileCleaner> <<::{::*.tmp; *.temp; *.gid; *.chk; *.~*;::}{:::}{:-1,1-0,2-0,3-0,4-0,5-0,6-0,7-0::}{:::}{:::}{:-0,1-0,2-0,3-0,4-0,5-0,6-0,7-0::}{:::}{::\Temp\|<br>|C:\Users\Owner\AppData\Local\Temp\|<br>|C:\Windows\Temp\::}{:-0,1-0,2-0,3-0,4-0::}{::~DF|<br>|Avast|<br>|FXSAPI|<br>|Recycle|<br>|Backups|<br>|Boot|<br>|-OPA11.BAK|<br>|media licenses|<br>|Ad-Aware 2007|<br>|Spybot - Search & Destroy|<br>|Users\Owner\Desktop\|<br>|BCD|<br>|hijack|<br>|\CBS\|<br>|\DPX\|<br>|\SoftwareDistribution\|<br>|\catroot2\|<br>|\SMI\Store\Machine|<br>|\wbem\|<br>|C:\Windows\WindowsUpdate.log|<br>|\winsxs\|<br>|\Debug\|<br>|\MSS|<br>|\LocalService\AppData\|<br>|\Windows Defender\|<br>|\Search\Data\Temp\usgthrsvc\|<br>|\hsperfdata_Owner::}::>>
<Terminate>

Added note: in retests, the "shows no window" and cpu/kill issues did not happen. They must have been due to something other than PT. However, the "deletes nothing" happened every time! If you remove <Terminate> from the jvb, then the tool works fine.

Please see Beta 4 update . . .

tlstevens

When running registry cleaner it shows userassist files leading to files that have been deleted. I have tried fixing them and also tried deleting them but when I run the scan again the same files show up.

This is an example of the registry entry referenced

HRZR_EHACNGU:\Hfref\Genpl\Qbjaybnqf\Cyhtvaf\InaQreYrr Znfgre Ohaqyr Pbyyrpgvba 2008 Sbe Cubgbfubc\

I have tried running the scan several times and even restarted the computer between scans, it shows the same results.

tullik

System Optimizer

Upon starting the PT2009 System Optimizer tool after a registry backup and system restart, none of the 22 tweaks were checked. So I checked all of them and clicked the Apply button.

This is what happened:

1. A backup subdirectory for all 22 tweaks appeared in ...\Backups\_SystemOptimizer. Each subdirectory contained an Index.dat and an Entries.reg. So far, so good …

2. All of the 22 tweaks stayed checked.

3. However, when I exited the S.O. tool and immediately started it again, the 1-9 tweak was no longer checked. As before, the 1-9 data type in the registry had been changed to REGDWORD, which seems to be incorrect! That is, it doesn't match with the backup.

4. When I recheck the 1-9 tweak and click Apply, the program replaces the 1-9 backup with the double word incorrectly placed in the registry at item 1 above. Now, at this point, the backup for 1-9 is no good! And both the backup and the registry key have the same invalid value!!! :

Next, I unchecked all 22 tweaks and clicked the Apply button.

This is what happened:

1. The backup subdirectories for all 22 tweaks were still in ...\Backups\_SystemOptimizer. Each subdirectory contained an Index.dat and an Entries.reg. So far, so good … except, as described above, the backup for 1-9 is still no good (a dword value).

2. All of the 22 tweaks stayed unchecked.

3. However, when I exited the S.O. tool and immediately started it again, the 2-11 tweak was again checked. At this point, the backup Entries.reg for 2-11 contained this:
""""=-In the registry, that key has no name or value.

4. Added note: The backed up (then restored) registry does not even have that key. So the 2-11 bug is triggered by a key-does-not-exist situation.

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

Conclusion: the tweak activation/undo mechanism in System Optimizer seems to be working except for tweaks 1-9 and 2-11.

System Optimizer, unreliable "undo" due to backup & apply bugs . . . . . . . . . . Partly fixed in PT2009 beta3 . . . (1)