Reg Cleaner & Softw Mgr BETTER in PT 2006 than in 2007

roberta

Good Day,

I am using both jv16 Powertools 2006 & 2007 on the same PC, so as to compare them.

jv16 PT 2006 ver 1.5.2.350

versus

jv16 PT 2007 ver 1.7.0.399

I have found the following discrepancies/differences after only trying the Registry Cleaner & the Software Manager.

Due to these discrepancies I have decided to put PT 2007 on indefinity hold until the following are commented on...

(a). Registy Cleaner (in Normal mode):

PT 2006 finds 575 Errors (469 High, 51 Medium, 41 Low, 14 Lowest),

Whereas

PT 2007 finds ONLY 346 Errors (223 High, 60 Medium, 63 Low)

PT 2006 v1.5.2.350 seems to have a MORE thorough Registry Cleaner.

Why the discrepancy?

(b). Software Manager:

PT 2007 doesnt find 3 installed modules that PT 2006 finds.

etc, etc, etc....

As a Very long user & supporter of jv16 (having also recommended it to all our contacts) I am Very Concerned regarding PT 2007's reliability & effectiveness.

Could Juonio Please comment on the findings as per above, & clarify the situation.

Thank You Very Much,

Best wishes,

Roberta

jv16

roberta wrote

(a). Registy Cleaner (in Normal mode):

PT 2006 finds 575 Errors (469 High, 51 Medium, 41 Low, 14 Lowest),

Whereas

PT 2007 finds ONLY 346 Errors (223 High, 60 Medium, 63 Low)

PT 2006 v1.5.2.350 seems to have a MORE thorough Registry Cleaner.

Why the discrepancy?

The programs show a different number of results because they work with a different registry cleaning engine. Usually comparing registry cleaner by just comparing the number of entires found doesn't make any sense because the validity of the errors is what counts, not the number.

But in this case you are right. There were some major changes in the engine between 2006 and 2007, perhaps the biggest ever. Such large changes can cause to problems so we tried to do everything as safe as possible. It turns out that we were playing a bit too safe in some cases, the latest version 399 fixed two bugs that caused valid registry errors to be ignored by the engine.

Actually, I'm working on the matter right now, I'm hopeful to find new similar bugs from the engine and improve its performance for the next release.

roberta wrote

(b). Software Manager:

PT 2007 doesnt find 3 installed modules that PT 2006 finds.

What 3 are them?

roberta

Greetings & Salutations jv16,

Thank You Very Much for your comments...,

..will "anxiously" wait for a FAR better PT 2007 release....

Unfortunately I set up an old hard drive with an old backup image strictly for testing new software (including PT2007) before installing in my personal production PC....

..& I wiped it out (& the orig bup image) after completing the testing.....

...But I remember that some Very Old codecs were not detected by the PT 2007 Software Manager.

Thank You Very Much,

Best wishes,

Roberta

PS:

Why does the startup of PT2007 take MUCH longer than that of PT2006 (just the display of the initial screen showing the different tools available)??...

tullik

roberta wrote
... PS:

Why does the startup of PT2007 take MUCH longer than that of PT2006 (just the display of the initial screen showing the different tools available)??...

I noticed the same thing, but even greater is the delay when you first start the Registry Cleaner. In the screenshot:

* The first short peak is when you launch PT2007 (about 5 seconds long)

* The second peak occurs when you start Registry Cleaner, which runs for about 100 to 120 seconds

* The trough at the start lasts a pretty constant 15 seconds -- during this time all active PT windows are unresponsive

* When RC finishes, if you immediately restart it, you see the about 1.5 minute peak when it rescans

* The rescan does not have the leading 15 second period of unresponsiveness

* So what is going on here in the leading 15 seconds? This cpu behavior is about the same in v.1.7.0.394, 398, and 399.

Windows Task Manager performance screenshot for PT2007 Registry Cleaner (green=total cpu, red=kernel cpu)

Shot at 2007-07-11

jv16

I have also noticed that the PT 2007 startup takes longer than before. I find it very annoying myself, but I'll have to focus on fixing the issues of the Registry Cleaner before it.

Speaking of the Registry Cleaner, I have some good news. I found two more bugs from it that causes valid errors not to be listed. One of the bug is rather theoretical, it could cause this but I couldn't verify it on my test environment. But anyway, these two are now fixed. I still think there are a few more to fix, I'm spending most of today in finding those.

And by the way, if someone is concerned on the number of bugs found from the registry cleaner engine this is simply because it is a new engine and because we wanted to make it extra safe it contains a lot of new safety features. It's these safety features that are causing the problem of valid errors not being listed by the program, not any non-stable code in the engine or anything like that. In English: we made it a bit too safe.

roberta

Good Day,

jv16 wrote
I have also noticed that the PT 2007 startup takes longer than before. I find it very annoying myself, but I'll have to focus on fixing the issues of the Registry Cleaner before it.

I am glad I am not the only one that has noticed this Annoying and Unnecessary delays....

jv16 wrote

Speaking of the Registry Cleaner, I have some good news. I found two more bugs from it that causes valid errors not to be listed. One of the bug is rather theoretical, it could cause this but I couldn't verify it on my test environment. But anyway, these two are now fixed. I still think there are a few more to fix, I'm spending most of today in finding those.

Great!!

The more bugs fixed...,

..the happier we will All be....

jv16 wrote

And by the way, if someone is concerned on the number of bugs found from the registry cleaner engine this is simply because it is a new engine and because we wanted to make it extra safe it contains a lot of new safety features. It's these safety features that are causing the problem of valid errors not being listed by the program, not any non-stable code in the engine or anything like that. In English: we made it a bit too safe.

Agreed on all counts....,

..better be safe than sorry....

...particularly regarding the registry & its integrity....

Thank You Very Much,

Best wishes,

Roberta

jv16

I'm currently trying to optimize the registry cleaner engine to give it more speed, I also did some tweaks that make the program start faster.

An updated version with these improvements should be out tomorrow.

tullik

Great -- I'll post its cpu usage graph here so we can see the difference ...

roberta

Greetings & Salutations,

jv16 wrote
I'm currently trying to optimize the registry cleaner engine to give it more speed, I also did some tweaks that make the program start faster.

An updated version with these improvements should be out tomorrow.

Great news!....

..looking forward to the new build....

tullik wrote
Great -- I'll post its cpu usage graph here so we can see the difference ...

Superb!...

..it will be Very interesting to compare, & measure progress...

Thank You Very much,

Have a Great day,

Roberta

jv16

The updated version will be out by this week, maybe today, maybe tomorrow. There are some other improvements as well and these delayed the release of the new version but I think it will be worth the wait.

roberta

jv16 wrote
The updated version will be out by this week, maybe today, maybe tomorrow. There are some other improvements as well and these delayed the release of the new version but I think it will be worth the wait.

Waiting with Great interest!!....

Thank You,

Roberta

jv16

roberta wrote

Waiting with Great interest!!....

Thank You,

Roberta

It's finally released, check it out: http://www.macecraft.com/phpBB2/viewtopic.php?p=10395#10395

tullik

There is a pretty good improvement in the v.1.7.0.401 beta just released :) -- namely (refer to screenshot below):

* The first short 100% peak is the Task manager initializing …

* The next short group at about 50% is the launch of PT2007 (v1.7.0.401 beta) (about 4 seconds long)

* The first long group is the start of Registry Cleaner - it still has the initialization trough, but only runs for 88 seconds (versus ~120 seconds in v.1.7.0.399

* The second long group is the Registry Cleaner rescan -- 70 seconds (versus ~100 seconds in v.1.7.0.399

* Therefore, the trough lasts about 18 seconds

Windows Task Manager performance screenshot for PT2007 Registry Cleaner (green=total cpu, red=kernel cpu)

~~Shot at 2007-07-24~~

roberta

jv16 wrote

It's finally released, check it out: http://www.macecraft.com/phpBB2/viewtopic.php?p=10395#10395

Greetings & Salutations,

I will check out 1.7.0.404 released today (after Build 403 released 24/7 ago).....

Cheers & Best wishes,

Roberta

roberta

Good Day,

Hmmmmmm....

..the saga continues....

Have now tested the Registry Cleaner in jv16 PowertooI 1.7.0.404 vs jv16 PT 2006 1.5.2.350 on the same PC (which is only used for this).

During testing no other work/activity was done on the PC.

ie PC was reserved for this testing...

Only the Registry Cleaner was tested & compared.

jv16 PowertooI 1.7.0.404

PT 2007 1.7.0.404 still Very Slow to show first screen.

When shown to other users, most thought jv16 PT 2007 had failed....

Some even tried to launch it again....

This result based on 12 independent users, who very kindly helped out.

Results For Registry Cleaner

(1). Registry Cleaner Summary screen readability:

Difficult to read blue font on red backgound (jv16 PowertooI 1.7.0.404).

Suggest it be changed back to black font on red backgound (as in PT2006).

(2). PT 2007 1.7.0.404 still not as good as PT 2006 1.5.2.350

But better than PT 2007 ver 1.7.0.399.

(3). PT 2007 1.7.0.404 results Very Inconsistent.

Results on repeated runs show Wild variability.

results varied from:

HIGH=408 - Medium=87 - LOW=68 - LOWEST=0

to

HIGH=762 - Medium=86 - LOW=98 - LOWEST=0

to

HIGH=1114 - Medium=86 - LOW=128 - LOWEST=0

I have the results for PT 2006, & far more info & data if wanted.

As stated above Only the Registry Cleaner has been tested and compared.

Could we Please have feedback from jv,

Thank You Very much,

Roberta

jv16

roberta wrote
Good Day,

jv16 PowertooI 1.7.0.404

PT 2007 1.7.0.404 still Very Slow to show first screen.

When shown to other users, most thought jv16 PT 2007 had failed....

Some even tried to launch it again....

This result based on 12 independent users, who very kindly helped out.

This doesn't seem normal. What kind of computer did you use and does it have an antivirus product?

roberta wrote

(3). PT 2007 1.7.0.404 results Very Inconsistent.

Results on repeated runs show Wild variability.

Did you only run the Registry Cleaner three times in a row, or did you remove something with it between the runs?

roberta

Good Day jv,

jv16 wrote
roberta wrote

jv16 PowertooI 1.7.0.404

PT 2007 1.7.0.404 still Very Slow to show first screen.

When shown to other users, most thought jv16 PT 2007 had failed....

Some even tried to launch it again....

This result based on 12 independent users, who very kindly helped out.

This doesn't seem normal. What kind of computer did you use and does it have an antivirus product?

Btw, the screen appears Only marginaly faster in ver 1.7.0.404 compared to the prev ver 1.7.0.399.

The testbed is a "top of the line" corporate Dell PC with an Intel Core 2 Duo cpu (delivered about 6-8 weeks ago) into which I recovered a Windows XP Prof SP2 backup image used for testing.

It has Symantec Antivirus Corporate Edition 10.1.6.6000 (NOT Norton).

Note that PT 2006 has No issue with it, Nor does any other application or tool that we use and/or have used/tested.

jv16 wrote

roberta wrote

(3). PT 2007 1.7.0.404 results Very Inconsistent.

Results on repeated runs show Wild variability.

Did you only run the Registry Cleaner three times in a row, or did you remove something with it between the runs?

The system was Completely dedicated to testing jv16 PTs.

No other task or program was run during testing.

All runs were consecutive.

Sometimes got one of the results 2 or 3 times in a row,

while other times got the 3 results consecutively (in a row).

Obviously Nothing was removed from the registry between the runs.

Did a total of approx > 40 consecutive runs of PT 2007.....

..& about 15 runs of PT 2006...

As I said I have far more data, But those 3 sets of results ALWAYS recurred (& no other results ever ocurred)....

Btw, PT 2006's results were Far More consistent.

Cheers,

Roberta

jv16

roberta wrote

The testbed is a "top of the line" corporate Dell PC with an Intel Core 2 Duo cpu (delivered about 6-8 weeks ago) into which I recovered a Windows XP Prof SP2 backup image used for testing.

It has Symantec Antivirus Corporate Edition 10.1.6.6000 (NOT Norton).

Note that PT 2006 has No issue with it, Nor does any other application or tool that we use and/or have used/tested.

Could you create a debug log of the program's startup and post it here for an analysis?

You can do this by creating an empty file called "DebugMode.dat" under the installation directory of the program. Then, the next time you run the program a debug log is automatically saved to your Desktop.

roberta

Greetings jv16,

jv16 wrote
roberta wrote

The testbed is a "top of the line" corporate Dell PC with an Intel Core 2 Duo cpu (delivered about 6-8 weeks ago) into which I recovered a Windows XP Prof SP2 backup image used for testing.

It has Symantec Antivirus Corporate Edition 10.1.6.6000 (NOT Norton).

Note that PT 2006 has No issue with it, Nor does any other application or tool that we use and/or have used/tested.

Could you create a debug log of the program's startup and post it here for an analysis?

You can do this by creating an empty file called "DebugMode.dat" under the installation directory of the program. Then, the next time you run the program a debug log is automatically saved to your Desktop.

Will wait till new build is released this week....

..& then re-assess situation...

Btw, are You changing the color of the font back to black to improve readability?....

...as blue font/type on red background is Not a very good choice....

Cheers,

Roberta

jv16

roberta wrote

Btw, are You changing the color of the font back to black to improve readability?....

...as blue font/type on red background is Not a very good choice....

Yes, this problem will also be fixed in the next release.

~~Next Page »~~