News on PowerTools 2009

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.

jv16

And oh, in the case I haven't mentioned it (and you haven't noticed already) we are moving towards a policy of releasing an updated version of PowerTools less frequent but with more fixes and improvements included. This allows us to perform better and more in-depth in-house testing of the new version before the release to make sure we don't introduce any more problems while trying to fix old ones.

rdtmk5

Perfect approach!!! Thanks.

siliconman01

rdtmk5 wrote
Perfect approach!!! Thanks.

I noticed and I agree totally.

jv16

I'm very happy to tell you that after many long nights working with Alex from Russia the the 64 bit Windows support is coming along very nicely. Many parts of the product are already fully compatible with 64 bit Windows, such as the Registry Finder and the creation of backups of this data works as well. I'm hoping to release a private build here in the forum tomorrow.

doogie

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.

stankay

jv16 wrote
I'm very happy to tell you that after many long nights working with Alex from Russia the the 64 bit Windows support is coming along very nicely. Many parts of the product are already fully compatible with 64 bit Windows, such as the Registry Finder and the creation of backups of this data works as well. I'm hoping to release a private build here in the forum tomorrow.

I too am fully over to 64 bit so your work will be geatly appreciated. I look forward to it's release.

rdtmk5

Jouni, there really wasn't any place else to post this very minor interface error problem (this is more like a beta test comment), but in Registry Cleaner, after Current file reference at the top of the screen, the colon (:) is missing. This must have happened with the latest release. Thanks.

jv16

rdtmk5 wrote
Jouni, there really wasn't any place else to post this very minor interface error problem (this is more like a beta test comment), but in Registry Cleaner, after Current file reference at the top of the screen, the colon (:) is missing. This must have happened with the latest release. Thanks.

Thanks, that's now fixed!

boofo

rdtmk5 wrote
Jouni, there really wasn't any place else to post this very minor interface error problem (this is more like a beta test comment), but in Registry Cleaner, after Current file reference at the top of the screen, the colon (:) is missing. This must have happened with the latest release. Thanks.

I was going to report that very same thing a few weeks ago but thought I would get jumped on for being a perfectionist. That has been like that since the first release of PowerTools 2009, by the way.

jv16

FYI: I'll release later today a new version of PowerTools containing all the fixes of the latest test build, but without the almost-working x64 support. Instead, the entire support for 64 bit registry view will be disabled, this should be a rather fail-safe option (i.e. the new version can be safely used with 64 bit Windows, it just doesn't analyze the entire registry).

The reason is that the x64 support may still take a few weeks to get right, I see no reason why the other users should wait this long for the updated version (with many other bug fixes and improvements).

jv16

Updated version released.

rdtmk5

Version 1.9.0.548. After 35 minutes, Registry Cleaner on most aggressive setting is stuck at 2 threads running (about 90%) complete. This is new behavior.

jv16

rdtmk5 wrote
Version 1.9.0.548. After 35 minutes, Registry Cleaner on most aggressive setting is stuck at 2 threads running (about 90%) complete. This is new behavior.

What about normal scan?

rdtmk5

Normal scan completes as expected.

rdtmk5

Interesting. Ran previous Registry Cleaner on aggressive yesterday evening - successfully cleaned all errors. Just ran a normal strength Registry Cleaner scan on the latest version - found 1,750 errors - 1,556 of them designated as Unneeded shared component entries. And after yesteday's scan, I turned my computer off, so there was no new registry activity. I haven't had this many registry errors since I first ran PT2007 years ago!

The debug log is attached.

jv16

jv16 wrote
Updated version released.

And I forgot to mention this: The 1.9.0.548 version has all the x64 compatibility fixes turned off. This was done to make sure that none of those x64 specific changes (that are not yet fully tested) cause any problems to the majority of users who use 32 bit operating systems.

siliconman01

The x64 mislocated SharedDLLs are still showing up in 1.9.0.548. Unsuspecting x64 users may lose a lot of their Shared DLL registry keys if they unknowingly run registry cleaner. Assuming us x64 users will still get the "Update Available" message from the previous version of PT 2009.

jv16

siliconman01 wrote
The x64 mislocated SharedDLLs are still showing up in 1.9.0.548. Unsuspecting x64 users may lose a lot of their Shared DLL registry keys if they unknowingly run registry cleaner.

Are you referring those Shared DLL entries with usage value of 0? These items are safe to be removed, x64 or not.

siliconman01

jv16 wrote
siliconman01 wroteThe x64 mislocated SharedDLLs are still showing up in 1.9.0.548. Unsuspecting x64 users may lose a lot of their Shared DLL registry keys if they unknowingly run registry cleaner.

Are you referring those Shared DLL entries with usage value of 0? These items are safe to be removed, x64 or not.

Yes, HOWEVER, as I stated before ALL of my SharedDLLs show a Reg_DWord value of 0x0000001 or greater. There are none that have a value of 0. This is via the normal x64 regedit. I don't know why they show up as 0 in PT 2009.

I "suspect" that PT 2009 is picking up a value of 0 because it has identified from the wrong location on x64.

Note, the ones being "falsely" detected are in the attached Wow6432SharedDLLs.

« Previous Page Next Page »