jv16 PowerTools 2010 Beta6 released! (Latest build: 938)

thmck

I tried the new Registry Compactor. It seamed to work and rebooted, however I'm not

sure of what it did. I found these files:

C:\Program Files\jv16 PowerTools 2010 Beta6\RegCompact\log.tex

C:\compactoutput.datcompactoutput.7zlog.7z

siliconman01

Windows 7 x64 Professional.

I ran the Compactor on Win 7 x64 Professional. It "appears" to have run and rebooted. However, no success messages were ever issued stating that it was completed properly. I did run the reg compactor of TuneUp Utilities and it stated that the registry was optimized and no compaction needed. Attached are the debug log and compact log.

We need some type of "Compact Completed" message following the reboot to let us know.

jepe

XP-Home / SP3

PT 2010 Compactor shows me, very quickly after Start, the message: "It wasn't possible to compact ... Most likely the are allready compacted.",

but PT 2009 Compactor found several hives it could compact a bit more.

Jean-Paul

siliconman01

Windows 7 x86 Professional

On Windows 7 x86, the Compactor ran and rebooted. It does show some failures in the log.

leonardo

Running XP-Prof SP3 with jv16PT-beta6-v927:

1. Resizing of the PT16 windows is still not remembered, this was already the case in beta2, beta3 and beta4:

-- Resizing the window right side border line is always lost (the right side border line seems to return to a fixed default position)

Resizing of the bottom border line is not remembered in a few cases.

2. Just for test purposes I uninstalled Zonealarm Antivirus, rebooted and ran registry finder on key 'zonealarm'.

-- 64 leftover registry hits found on key 'zonealarm'. Deleted the 64 entries with a backup. Reran registry finder, 0 entries found on key 'zonealarm'.

Restored the taken backup with 64 entries. Restore was reported succesfull.

Closed beta6, Rebooted, Restarted beta6, reran registry finder on key 'zonealarm' and 0 entries found.

Conclusion: Restore is not functioning?

-- I did a similar test on the results of a most aggresive registry scan, found 115 entries "invalid file or directory reference", used 'Fix' with a backup.

Repeated the registry scan, 0 entries "invalid file or directory reference" found. Restored the taken backup,

Rescanned the registry, scan result is 1 found entry "invalid file or directory reference", The rest (114?) are not restored in the registry.

redseujac

siliconman01 wrote
Windows 7 x64 Professional.

I ran the Compactor on Win 7 x64 Professional. It "appears" to have run and rebooted. However, no success messages were ever issued stating that it was completed properly...We need some type of "Compact Completed" message following the reboot to let us know.

That's exactly what I reported previously to Jouni too.

I saw nothing at all during reboot. Besides when I compared the hive sizes before and after the process they remain exactly the same. I ran TuneUp Registry Defrag and it worked as it should: difference from current size: 3.036 KB (5%).I got the reboot with the DOS like environment and the indication of the progress and afterwards a new reboot. When in GUI again appeared a message : the registry has been optimized with new size and difference from before.

Jouni ensures that with Registry Compactor we also should have the progress message while rebooting, but it fails on my system and besides the hives are not compacted. I think it's an issue or bug in beta6 for Win7 x64 OS.

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.

thmck

Today when I started my computer the Registry Compactor tried to start.

I rebooted again, same thing. I found this file "C:\WINDOWS\system32\jv16pt_regcompact_32.exe" and renamed it. Now on reboot it does'nt try to start

the Compactor.

jv16

Leonardo wrote

2. Just for test purposes I uninstalled Zonealarm Antivirus, rebooted and ran registry finder on key 'zonealarm'.

-- 64 leftover registry hits found on key 'zonealarm'. Deleted the 64 entries with a backup. Reran registry finder, 0 entries found on key 'zonealarm'.

Restored the taken backup with 64 entries. Restore was reported succesfull.

Closed beta6, Rebooted, Restarted beta6, reran registry finder on key 'zonealarm' and 0 entries found.

Conclusion: Restore is not functioning?

You are correct! This is a rather serious bug in the Beta6. The Beta6 creates incorrect registry backups, the registry backup files lack the required header and therefore cannot be restored back to the registry. It's easy to manually fix the incorrectly created registry backup files, so this issue isn't that serious.

This issue is already fixed, it was the problem detected by the Unit Testing tool and I fixed the issue a while ago already.

An updated version of the Beta6 with this issue fixed, and the Anti-Malware feature ready, will probably be released on Monday. The next version does not yet contain fix to the Registry Compactor issue, I'm afraid.

jv16

thmck wrote
Today when I started my computer the Registry Compactor tried to start.

I rebooted again, same thing. I found this file "C:\WINDOWS\system32\jv16pt_regcompact_32.exe" and renamed it. Now on reboot it does'nt try to start

the Compactor.

If this occurs again, you can run the unset.exe from jv16 PowerTools\RegCompact\ directory, it removes the Registry Compactor from being automatically started by Windows during startup.

leonardo

jv16 wrote

You are correct! This is a rather serious bug in the Beta6. The Beta6 creates incorrect registry backups, the registry backup files lack the required header and therefore cannot be restored back to the registry. It's easy to manually fix the incorrectly created registry backup files, so this issue isn't that serious.

Please inform me how to manually fix the incorrectly created registry backup files?

jv16

Leonardo wrote
jv16 wrote

You are correct! This is a rather serious bug in the Beta6. The Beta6 creates incorrect registry backups, the registry backup files lack the required header and therefore cannot be restored back to the registry. It's easy to manually fix the incorrectly created registry backup files, so this issue isn't that serious.

Please inform me how to manually fix the incorrectly created registry backup files?

Open up the registry backup file in question (Entries.reg), and add the following line as the first line of the Entries.reg:

Windows Registry Editor Version 5.00

That is all you need to do. After that, PowerTools will be able to restore the backup. Or, you can restore it yourself by double clicking the .reg file.

leonardo

jv16 wrote
Leonardo wrote
jv16 wrote

You are correct! This is a rather serious bug in the Beta6. The Beta6 creates incorrect registry backups, the registry backup files lack the required header and therefore cannot be restored back to the registry. It's easy to manually fix the incorrectly created registry backup files, so this issue isn't that serious.

Please inform me how to manually fix the incorrectly created registry backup files?

Open up the registry backup file in question (Entries.reg), and add the following line as the first line of the Entries.reg:

Windows Registry Editor Version 5.00

That is all you need to do. After that, PowerTools will be able to restore the backup. Or, you can restore it yourself by double clicking the .reg file.

Thank you, that solved my Beta6 BackUp restore problems

leonardo

Registry Finder results (for the same keyword) vary between Beta4 and beta6:

I tested a Registry Finder scan with keyword = babylon.

Although the number of hits found is almost equal, 109 versus 110, the content/hives do differ!

See attatched zip file with the saved files from the Registry Finder scans, with keyword = babylon, for Beta 4 and Beta6.

ADDED COMMENT:

I also did a Registry Finder scan with keyword = zonealarm.

38 hits versus 66 hits!

See attatched zip file with the saved files from the Registry Finder scans, with keyword = zonealarm, for Beta 4 and Beta6.

jv16

Leonardo wrote
Registry Finder results (for the same keyword) vary between Beta4 and beta6:

I tested a Registry Finder scan with keyword = babylon.

Although the number of hits found is almost equal, 109 versus 110, the content/hives do differ!

Could you please send a screenshot of the Registry Finder's Options tab so I can see what options you are using. I am assuming you used the same options with both versions?

leonardo

jv16 wrote
Leonardo wroteRegistry Finder results (for the same keyword) vary between Beta4 and beta6:

I tested a Registry Finder scan with keyword = babylon.

Although the number of hits found is almost equal, 109 versus 110, the content/hives do differ!

Could you please send a screenshot of the Registry Finder's Options tab so I can see what options you are using. I am assuming you used the same options with both versions?

I checked ALL Registry Finder options to make sure they are the same for beta4 and beta6

I reran the Registry Finder scans (beta4 + beta6) with keyword = zonealarm.

The screenshot + scan results are in the attached zonealarm.zip file.

If needed I can do the same for keyword = babylon

jv16

Leonardo wrote

If needed I can do the same for keyword = babylon

Could you do the same test with "Use approximate search" option turned off?

jv16

Leonardo wrote
Running XP-Prof SP3 with jv16PT-beta6-v927:

1. Resizing of the PT16 windows is still not remembered, this was already the case in beta2, beta3 and beta4:

-- Resizing the window right side border line is always lost (the right side border line seems to return to a fixed default position)

Resizing of the bottom border line is not remembered in a few cases.

Can anyone else reproduce this issue?

leonardo

jv16 wrote
Leonardo wrote

If needed I can do the same for keyword = babylon

Could you do the same test with "Use approximate search" option turned off?

I just repeated the test with "Use approximate search" option turned off"

see the attached zonealarm_02.zonealarm_02.zipzip file

jv16

FYI: Everyone using the latest Beta6 build should now see a warning about the registry backup problem, when using the Check for Updates feature. This is mainly to test the warning features of PowerTools 2010, none of these were possible with PT 2009. 8)

And starting with the next build, user doesn't even have to open the Check for Updates, we can send messages to all PowerTools users over the Internet. For example, to the Message Panel of the Main Window, or as a popup message. These features are used in a case a serious bug is found from the program.

« Previous Page Next Page »