Test version 1.9.0.581 released (and now: 590)

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.

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.

thomas-k

Smal Bug in "jv16 PowerTools 2009 - Registry Manager"

The entry "Search menu" from the "pulldown menu" of the "Section" part of the Registry Manager is without function; also the short key Shift+F7. I found and posted this smal Bug in the Bugtracker for weeks, is it a problem to fix this smal issue?

SearchMenu.png

tullik

jv16 wrote
... But on the other hand, fixing the errors, even if it means that all but one entry is removed, is better in a case this issue causes a 3rd party program error, than simply deleting all the items.

It's a matter of should we fix 1 entry instead of 4 (because you can't fix all 4), OR delete them all. In my opinion, fixing the one item would be better.

Wouldn't you think so?

Well, it doesn't actually fix anything in this case. It just makes the item not appear as an error in the Registry Cleaner. The end result in my posted case was 6 historical items which existed at one time were replaced with a single item that never happened, and its data came randomly from one of the 6.

jv16

thomas-k wrote
Smal Bug in "jv16 PowerTools 2009 - Registry Manager"

The entry "Search menu" from the "pulldown menu" of the "Section" part of the Registry Manager is without function; also the short key Shift+F7. I found and posted this smal Bug in the Bugtracker for weeks, is it a problem to fix this smal issue?

Problem confirmed and fixed. Thanks for reminding me!

jv16

tullik wrote

Well, it doesn't actually fix anything in this case. It just makes the item not appear as an error in the Registry Cleaner. The end result in my posted case was 6 historical items which existed at one time were replaced with a single item that never happened, and its data came randomly from one of the 6.

In this case it doesn't fix anything, but in some other case with similar data it could. And since it neither causes any problems, I feel this is the correct way to handle these rare kinds of cases.

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.

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.

tullik

tullik wrote
jv16 wrote... But still, in your opinion, how should cases like these be fixed?
...

I'm scanning the registry now (for C:\) to see what other type keys have a path in the name ...

There are 4801 entries in total.

Some like and ...\muicache\... seem to have mainly a historical purpose. Many entries are never, or hardly ever, used now.

These appear safe to remove (so I did), but the entries will build up again over time:

118 (...\billp studios\Detected\ActiveTasks\)

324 (HKUS\.Def\Soft\MSoft\Win\shell\muicache\) + 324 (HKUS\s-1-5-18\Soft\MSoft\Win\shell\muicache\)

240 (HKCU\Soft\classes\local settings\Soft\MSoft\Win\shell\muicache\) + 240 (HKCR\local settings\Soft\MSoft\Win\shell\muicache\)

Total of the above = 1246 entries (~25% of 4800)

Perhaps the PT2010 History Cleaner could include the "muicache" items periodically, say every 60 to 90 days.

Also, will the PT2010 Registry Finder have a caption area "explore" feature for items with a path in the name or data? For example:

HKLM\Soft\MSoft\Win\CurVer\installer\Folders\ (~32% of 4800)

HKLM\Soft\MSoft\Win\CurVer\shareddlls\ (~34% of 4800)

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

FYI: an official version has now been released, big thanks to everyone who helped!

If nothing major is found, this might be the last release of PT 2009. The code has been already branched to PowerTools 2010 and its development has been going on for months by my collegues, now I will be joining them. And my first task is nothing less than to create the 6th generation of the Registry Cleaner engine.

hawkeyelom

It has taken several months to fix bugs and bring 2009 up to snuff----

Friendly suggestions: Contimue to fix bugs in 2009 and PL don't release 2010 until it is rock solid--no known bugs and works perfectly with Vista 64 bit and both 32 bit and 64 bit version of Windows 7

« Previous Page