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

roberta

Good Day JV,

Is jv16 PowerTools 2007 1.7.0.405 worth evaluating/testing?

Have any of the issues I have raised before been fixed &/or addressed?

Particularly:

(1). The Very Different results from the Registry Cleaner in subsequent runs (done immediately after each other,

and without having fixed any errors between runs).

Please refer to my previous results above.

And what many other users have raised before:

(2). jv16 PowerTools 2007 1.7.0.405 does Not work on Windows 98SE.

This has been a problem for quite a few builds...

..& has Not been fixed Yet....

I have noticed the decreased postings here re PT2007, and I believe it is most likely due to a lot of users just giving up on it...

..& that is brought out by my discussion elsewhere with other users & prospective users.....

PTs 2007 seems to have caused a crisis in trust for the reliability & effectiveness of jv16 PowerTools.....

...& that is Unfortunate & Undesirable.

Could we Please have feedback/information re the issues I have raised?....

Thank You,

Roberta

jv16

roberta wrote

Have any of the issues I have raised before been fixed &/or addressed?

Particularly:

(1). The Very Different results from the Registry Cleaner in subsequent runs (done immediately after each other,

and without having fixed any errors between runs).

Please refer to my previous results above.

Could someone else please verify this problem? I haven't been able to reproduce it, nor do I remember anyone else reporting it either.

And what many other users have raised before:

(2). jv16 PowerTools 2007 1.7.0.405 does Not work on Windows 98SE.

This has been a problem for quite a few builds...

..& has Not been fixed Yet....

There have been changes in order to fix the problem in numerous builds, so far the problem hasn't been fixed. It's not our top priority to fix the problem since Windows 98 is a rather obsolete system.

I have noticed the decreased postings here re PT2007, and I believe it is most likely due to a lot of users just giving up on it...

I disagree. Usually the forum has a lot of messages and we get a lot of user feedback when there are many obvious and easy-to-find bugs in the product, when these bugs are fixed the number of topics and user feedback decreases.

But the one figure I trust the most is our sales: people do vote with their wallets, and these votes confirm that people really like jv16 PowerTools 2007, it is selling way better than any previous versions. Also the ratio of refunds and cancelled orders have remained low, under 1%.

Or, see our reviews: http://www.macecraft.com/reviews/

People haven't "given up on" jv16 PowerTools 2007, that's just nonsense.

bobkat

JV16 Please don't dismiss or abandon Win 98 users. Although it is an older OS, there are still a number of us who patch and tweak and continue to use. I hope that you can still fix the problem and we can continue to enjoy all of your updates.

jv16

Bobkat wrote
JV16 Please don't dismiss or abandon Win 98 users. Although it is an older OS, there are still a number of us who patch and tweak and continue to use. I hope that you can still fix the problem and we can continue to enjoy all of your updates.

Of course, I will do everything I can to get the product working wth Win9x again. I'll try to find time to focus on this problem for the next version.

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.

tullik

thiggy wrote
... Maybe an older version of jv16 would be better used with Win98; maybe a free version from the past.

Or PT2007 v.1.7.0.394 -- apparently that works with win98 ...

roberta

roberta wrote

(1). The Very Different results from the Registry Cleaner in subsequent runs (done immediately after each other,

and without having fixed any errors between runs).

Please refer to my previous results above.

Good Day,

What concerns me is that the Registry Cleaner in PT 2007 consistently detects Far Less errors than PT 2006 Build 350....

..& the number of errors detected by PT 2007 show a Huge variability....

...whereas PT 2006 is Far More consistent.....

Cheers,

Roberta

tullik

Some Registry Cleaner differences, PT2006 vs. PT2007

It is impossible to conclude anything useful from the High/Medium/Low/Lowest measure. That measure is OK as eye candy, but analysis requires a different approach, such as the example here.

It also very difficult to make sense out of hundreds of observations of mixed types. Therefore, I did a limited analysis of the "File or Directory 'path' does not exist" error type. The items found by PT2007 and by PT2006 are shown at the end of this post. Both scans occurred on my Vista desktop.

Observations:

1. PT2007 found only the six red items. PT2006 found the same ones, plus several others.

2. The blue items found by PT2006 are duplicates. Some are outright duplicates (a rather harmless bug in PT2006). Others are "synonyms" (or "twins") automatically created by windows. Removing either of the twins causes windows to remove automatically the other. It is actually a good thing that PT2007 does not list both such synonyms (I hope that was done in PT2007 on purpose :| ).

3. The two underlined items are twins not detected as such by PT2007 …

4. I think I know why the green items were not listed by PT2007. However, I don't intend to make it an issue until more important issues are resolved.

5. I have no theory about the violet item.

PT2007 scan result

jv16 PowerTools 2007

Data fields are: Error severity, Key, Entry's name, Value, Error description, Entry last modified

High, HKCU\Soft\MSoft\MPEG2Demultiplexer\, WriteCaptureDir, c:\dm.capture\, File or directory "c:\dm.cap" does not exist, 08.08.2007, 05

Low, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\Classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe" does not exist, 09.08.2007, 04

Low, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\Classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist, 09.08.2007, 04

High, HKCU\Soft\MSoft\Win\CurVer\Explorer\UserAssist\ {75048700-EF1F-11D0-9888-006097DEACF9}\Count\, HRZR_EHACNGU:\Cebtenz Svyrf\wi16 CbjreGbbyf\Irefvbaf\ErtFhcerzr Ceb orgn1\ErtFhcerzr Ceb\ErtFhcerzrCeb.rkr, N/A, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist, 09.08.2007, 13

High, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\MSoft\Win\CurVer\Explorer\UserAssist\ {75048700-EF1F-11D0-9888-006097DEACF9}\Count\, HRZR_EHACNGU:\Cebtenz Svyrf\wi16 CbjreGbbyf\Irefvbaf\ErtFhcerzr Ceb orgn1\ErtFhcerzr Ceb\ErtFhcerzrCeb.rkr, N/A, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist, 09.08.2007, 13

High, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\MSoft\MPEG2Demultiplexer\, WriteCaptureDir, c:\dm.capture\, File or directory "c:\dm.cap" does not exist, 08.08.2007, 05

PT2006 scan result

jv16 PowerTools 2006

Data fields are: Error severity, Key, Entry's name, Value, Error description

High, HKCU\Soft\MSoft\MPEG2Demultiplexer\, WriteCaptureDir, c:\dm.capture\, File or directory "c:\dm.cap" does not exist

Lowest, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\Classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe" does not exist

Lowest, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\Classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist

High, HKCU\Soft\MSoft\Win\CurVer\Explorer\UserAssist\ {75048700-EF1F-11D0-9888-006097DEACF9}\Count\, HRZR_EHACNGU:\Cebtenz Svyrf\wi16 CbjreGbbyf\Irefvbaf\ErtFhcerzr Ceb orgn1\ErtFhcerzr Ceb\ErtFhcerzrCeb.rkr, N/A, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist

High, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\MSoft\Win\CurVer\Explorer\UserAssist\ {75048700-EF1F-11D0-9888-006097DEACF9}\Count\, HRZR_EHACNGU:\Cebtenz Svyrf\wi16 CbjreGbbyf\Irefvbaf\ErtFhcerzr Ceb orgn1\ErtFhcerzr Ceb\ErtFhcerzrCeb.rkr, N/A, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist

High, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\MSoft\MPEG2Demultiplexer\, WriteCaptureDir, c:\dm.capture\, File or directory "c:\dm.cap" does not exist

Lowest, HKCR\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe" does not exist

Lowest, HKCU\Soft\Classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe" does not exist

Lowest, HKLM\Soft\classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe" does not exist

Lowest, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\Classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe" does not exist

Lowest, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010_Classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools 2007 v.1.7.0.404 (vanilla)\jv16PT.exe" does not exist

Lowest, HKCR\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist

Lowest, HKCU\Soft\Classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist

Lowest, HKLM\Soft\classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist

Lowest, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010_Classes\Local Settings\Soft\MSoft\Win\shell\MuiCache\, C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe, jv16 PowerTools 2007, File or directory "C:\Program Files\jv16 PowerTools\Versions\RegSupreme Pro beta1\RegSupreme Pro\RegSupremePro.exe" does not exist

High, HKUS\S-1-5-21-2736614755-4186107725-1336004102-1010\Soft\MSoft\MPEG2Demultiplexer\, WriteCaptureDir, c:\dm.capture\, File or directory "c:\dm.cap" does not exist

High, HKCR\Installer\Products\89C0CF46530B03541BD5D30316B0D61F\SourceList\Net\, 1, c:\hp\drivers\hpiz454\setup\HPSoftwareUpdate\, File or directory "c:\hp\drivers\hpiz454\setup\HPSoftwareUpdate\" does not exist

High, HKLM\Soft\classes\Installer\Products\89C0CF46530B03541BD5D30316B0D61F\SourceList\Net\, 1, c:\hp\drivers\hpiz454\setup\HPSoftwareUpdate\, File or directory "c:\hp\drivers\hpiz454\setup\HPSoftwareUpdate\" does not exist

High, HKCR\Installer\Products\C4A3430EDFF2BCC40BBED59E0F2E0A38\SourceList\Net\, 1, c:\hp\drivers\LightScribe\, File or directory "c:\hp\drivers\LightScribe\" does not exist

High, HKLM\Soft\classes\Installer\Products\C4A3430EDFF2BCC40BBED59E0F2E0A38\SourceList\Net\, 1, c:\hp\drivers\LightScribe\, File or directory "c:\hp\drivers\LightScribe\" does not exist

High, HKLM\Soft\MSoft\Windows NT\CurVer\Print\PackageInstallation\Windows NT x86\DriverPackages\ntprint.inf_a6d3ccdf\, CabPath, C:\Windows\system32\spool\DRIVERS\W32X86\PCC\ntprint.inf_a6d3ccdf.cab, File or directory "C:\Windows\system32\spool\DRIVERS\W32X86\PCC\ntprint.inf_a6d3ccdf.cab" does not exist

High, HKCR\Installer\Products\9F2FDFE0D6387BE43AD230B83D1FBFA2\SourceList\Net\, 1, C:\Windows\TEMP\IXP000.TMP\, File or directory "C:\Windows\TEMP\IXP000.TMP" does not exist

High, HKLM\Soft\classes\Installer\Products\9F2FDFE0D6387BE43AD230B83D1FBFA2\SourceList\Net\, 1, C:\Windows\TEMP\IXP000.TMP\, File or directory "C:\Windows\TEMP\IXP000.TMP" does not exist

High, HKLM\Soft\MSoft\Windows NT\CurVer\AppCompatFlags\Layers\, C:\Windows\System32\javacpl.cpl, RUNASADMIN, File or directory "C:\Windows\System32\javacpl.cpl" does not exist

jv16

roberta wrote

What concerns me is that the Registry Cleaner in PT 2007 consistently detects Far Less errors than PT 2006 Build 350....

..& the number of errors detected by PT 2007 show a Huge variability....

...whereas PT 2006 is Far More consistent.....

When you ran jv16 PowerTools 2007 many times on a row, how exactly did you do it?

Did you close the results window between each scan, or not?

roberta

jv16 wrote
roberta wrote

What concerns me is that the Registry Cleaner in PT 2007 consistently detects Far Less errors than PT 2006 Build 350....

..& the number of errors detected by PT 2007 show a Huge variability....

...whereas PT 2006 is Far More consistent.....

When you ran jv16 PowerTools 2007 many times on a row, how exactly did you do it?

Did you close the results window between each scan, or not?

Greetings & Salutations JV,

I ran the Registry Cleaner again after closing the results window after each scan...,

..& I also did a series of the same tests where between each Registry Cleaner run I closed the results window & Also the PTs window....

Cheers & Best wishes,

Roberta

tullik

@ roberta -- How many of the errors found in a typical run in your test environment have the Error description type "File or directory "path" does not exist"

with PT2006?

with PT2007?

And what are the total errors for each program?

On the Registry Cleaner's results window, Tools-->Search, then entering does not exist gives a count in the status bar …

tullik

tullik wrote
@ roberta -- How many of the errors found in a typical run in your test environment have the Error description type "File or directory "path" does not exist"
with PT2006?

with PT2007?
And what are the total errors for each?

On the Registry Cleaner's results window, Tools-->Search, then entering does not exist gives a count in the status bar …

@ roberta -- If you have the time, you could do the above for other high volume Error description types. I think that would likely help identify probable causes of the PT2006 vs. PT2007 difference in items found. Post the results here and they could give jv clues about where in the code to look for causes.

No need to do them all. Use the 80-20 rule (Pareto principle). And concentrate on ones with a significant difference between the two programs.

jv16

tullik wrote

Roberta's observations are, I think, valid, but only reproducible in the special environment she described. The experiment's assumption is probably that the scanning engine should behave much like an application program (given the same inputs, the outputs are always the same). However, the windows registry is too dynamic to be the same.

I agree, but the dynamic nature of the registry usually only explains minor differences between scans. By minor I mean less than 100. Of course, this depends highly on how many other programs and background processes are running when using the Registry Cleaner.

However, I did some improvements to the registry cleaner engine to prepare for the release of RegSupreme Pro 1.7 RC1 and out of the blue, there it was: I was able to reproduce the problem Roberta describes.

The number of errors found varied between 6000 and 9000 on scans done on a row - way more than one could except!

I'm trying to locate the problem and fix it for the RegSupreme Pro 1.7 RC1 which will be released later today.

roberta

tullik wrote
tullik wrote@ roberta -- How many of the errors found in a typical run in your test environment have the Error description type "File or directory "path" does not exist"
with PT2006?

with PT2007?
And what are the total errors for each?

On the Registry Cleaner's results window, Tools-->Search, then entering does not exist gives a count in the status bar …

@ roberta -- If you have the time, you could do the above for other high volume Error description types. I think that would likely help identify probable causes of the PT2006 vs. PT2007 difference in items found. Post the results here and they could give jv clues about where in the code to look for causes.

No need to do them all. Use the 80-20 rule (Pareto principle). And concentrate on ones with a significant difference between the two programs.

Good Day Tullik,

I believe this might wait till the next build is released (refer to JV's answer above)....

Cheers,

Roberta

roberta

jv16 wrote
tullik wrote

Roberta's observations are, I think, valid, but only reproducible in the special environment she described. The experiment's assumption is probably that the scanning engine should behave much like an application program (given the same inputs, the outputs are always the same). However, the windows registry is too dynamic to be the same.

I agree, but the dynamic nature of the registry usually only explains minor differences between scans. By minor I mean less than 100. Of course, this depends highly on how many other programs and background processes are running when using the Registry Cleaner.

However, I did some improvements to the registry cleaner engine to prepare for the release of RegSupreme Pro 1.7 RC1 and out of the blue, there it was: I was able to reproduce the problem Roberta describes.

The number of errors found varied between 6000 and 9000 on scans done on a row - way more than one could except!

I'm trying to locate the problem and fix it for the RegSupreme Pro 1.7 RC1 which will be released later today.

Greetings & Salutations JV,

Hurrah!!....

..I knew that sooner rather than later You would start resolving this issue....

Btw, as I said earlier the system had No other applications (ie No progs other than the OS) running while the testing was done (completely dedicated to testing PTs)....

Thank You,

Roberta

PS:

If You want figures as suggested by Tullik....

..Please let me know....

...otherwise I will wait for the next PT 2007 build....

Any idea when the new build with the correction(s) might be released?......

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.

roberta

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.

roberta

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

roberta wrote

RegSupreme Pro 1.7 RC1 (1.7.0.407) - 12 consecutive runs Registry Cleaner

HIGH: varied from 412 to 1126 errors

MEDIUM: 88 errors on 11 runs, 56 on 1 run

LOW: varied from 63 to 109 errors

LOWEST: 0

scan times: varied from 56 to 72 sec

OK, this doesn't seem right. But, just to be sure this doesn't have anything to do with your computer and all to do wth our product, could you do a few test runs on another computer with the RegSupreme Pro 1.7 RC1?

Btw, the initial screen of jv16 PT 2007 still takes Far too long to even come up.....

..Why?.....

Again I asked about ten users for their opinion re this....

..& Again most said they wondered whether something had gone wrong....

...& some asked what is jv16 PT 2007 doing before even displaying its first screen?.......

The startup (i.e. the time from double clicking the file to the window showing up) should take about 1 second on a computer with over 1 GHz cpu.

The program is doing lots of things at startup, for example detecting all the settings, searching for a license file, translating the program to the language of your choice etc.

I'll try to find something to fix.

redseujac

jv16 wrote
The startup (i.e. the time from double clicking the file to the window showing up) should take about 1 second on a computer with over 1 GHz cpu...I'll try to find something to fix.

I have no problem with the startup time which takes only a few seconds. Most of the users have no problem with it.

I wonder if there's something to be fixed.

« Previous Page Next Page »