jv16's development blog

boofo

I'll be curious to see that in action on my old P4 processor.

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

Another nice improvement of PowerTools 2010: you are no longer required to run the Quick System Analysis.

When you start the program for the very first time (or if you delete the contents of the \Cache directory) you'll need to wait for the "initial setup" to complete. This takes longer than the QSA of PT 2009, in which all caches are created, registry and file system analyzed, backups created of critical registry sections etc. It takes a few minutes to run.

The data generated in Quick System Analysis in PowerTools 2009 will be generated on-the-fly in smaller pieces in PowerTools 2010.

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.

jv16

After a long day at the office, the test version 7 for in-house testing is finally ready. The Quick System Analysis have been removed, the registry health bar of the main window is now automatically updated after the Registry Cleaner is run. Still need to add the same support for "Clean and fix my computer" feature, though.

Tomorrow I'll continue to plug in the fast registry access component and start to work with the "Clean and fix my computer" feature to get it ready for prime time as well. The actual Registry Cleaner itself seems to be ready for public beta testing already.

jv16

Today I have been fine tuning the fast registry access component and the Registry Cleaner Engine, a little bit of this and that, really.

The second stage of testing will start on Monday. In the second stage the test version is give to a few most active beta testers of the forum and a few other people outside of the company as well. The second stage is scheduled to last for one week, after that starts the public beta testing which is scheduled to last for at least one month.

boofo

Looking forward to it, Maestro. ;)

jv16

I have continued to fine tune the Registry Cleaner Engine, now from the point of view of performance.

And I have made some serious progress. When I started earlier today, the PT 2010's File Reference scan module (which usually takes the longest time in the registry scan) took 86.7 seconds. I then got it down to 73.4 seconds. And then to 62.7 seconds.

Compared to PowerTools 2009, its File Reference scan module takes 65 seconds. While the increase of speed might not sound very amazing yet, we must remember that so far I have only optimized the actual registry scanning and data analysis. Most of the time of the entire process is spent on the final analysis of data, if I can get 20 seconds away from there we are going faster than PowerTools has ever gone!

I'll probably work during the weekend (shame on me!) and mainly focus on the performance optimization of the Registry Cleaner Engine. At the moment the speed is good, but I want to make it "wow" :

jv16

The speed of the File Reference scan with PowerTools 2010 is now 37.2 seconds (vs. 65 seconds with PT 2009).

Now I'm working with the File Extension scan module, with PT 2010 it's taking now 28.21 seconds (vs. 32 seconds with PT 2009). Lets see how fast I can make it...

jv16

Alright, that's it for today. I got roughly two seconds from the File Extension scan's time, it was already rather well optimized so not much room for improvement.

Anyways, at the moment the performance looks the following (Registry Cleaner, full scan with default settings):

jv16 PowerTools 2009: 89 seconds.

jv16 PowerTools 2010: 60 seconds.

Tomorrow I'll be implementing the few good feature requests by Tullik (http://www.macecraft.com/phpBB3/viewtopic.php?f=13&t=3932). After that, I'll continue probably to optimize the Registry Cleaner Engine.

doogie

jv16 wrote
Alright, that's it for today. I got roughly two seconds from the File Extension scan's time, it was already rather well optimized so not much room for improvement.

Anyways, at the moment the performance looks the following (Registry Cleaner, full scan with default settings):

jv16 PowerTools 2009: 89 seconds.

jv16 PowerTools 2010: 60 seconds.

Tomorrow I'll be implementing the few good feature requests by Tullik (http://www.macecraft.com/phpBB3/viewtopic.php?f=13&t=3932). After that, I'll continue probably to optimize the Registry Cleaner Engine.

I feel that accuracy is preferable to speed Jouni. If you can get both then that's a bonus.

jv16

DooGie wrote

I feel that accuracy is preferable to speed Jouni.

Of course, and that is why I have spent 95% of my time with safety and accuracy, and yesterday was the first time I really sat down to improve the speed of the new engine.

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.

siliconman01

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.

doogie

tullik wrote
Windows Vista HP x64 and PT v.1.9.0.590

*** The Registry Cleaner category “Registry key with incorrect permissions or owner” is not consistent. Counts have varied from 444 (initially) to 0, but I have seen a count of 380 in three or four runs. (a bug?).

I posted about this in another thread tullik and posted a .txt file of the entries. http://www.macecraft.com/phpBB3/viewtopic.php?f=21&t=3891

jv16

tullik wrote
Windows Vista HP x64 and PT v.1.9.0.590

*** Not surprisingly, it makes no discernible difference whether PT is run from Program Files or from Program Files (X86).

*** Main window-->Shortcuts-->Accessories-->RegEdit invokes C:\WINDOWS\regedit.exe even when Settings points to C:\WINDOWS\SysWOW64\regedit.exe (a bug?).

I do not think that this is a bug, but I'll check it out.

tullik wrote

*** None of the file system Explore features work in any tool where I've tried them (a bug).

*** None of the “Open in RegEdit” features work in any tool where I've tried them (a bug).

Trying to fix these...

tullik wrote

*** The Registry Cleaner category “Registry key with incorrect permissions or owner” is not consistent. Counts have varied from 444 (initially) to 0, but I have seen a count of 380 in three or four runs. (a bug?).

This is now fixed.

tullik

jv16 wrote
tullik wrote Windows Vista HP x64 and PT v.1.9.0.590

...

*** Main window-->Shortcuts-->Accessories-->RegEdit invokes C:\WINDOWS\regedit.exe even when Settings points to C:\WINDOWS\SysWOW64\regedit.exe (a bug?).

I do not think that this is a bug, but I'll check it out. ...

I think you are right (not a bug).

In fact, I'm distrustful of the syswow64 regedit, for the following reason:

A top down search with SysWow64 regedit:
- 1 HKEY_CURRENT_USER\Software\Wow6432Node
  
  2 HKEY_USERS\.DEFAULT\Software\Wow6432Node
  
  3 HKEY_USERS\S-1-5-18\Software\Wow6432Node
  
  4 HKEY_USERS\S-1-5-21-1963773873-535440688-1456871427-1000\Software\Wow6432Node

A top down search with just regedit:
- 1 HKEY_CLASSES_ROOT\Wow6432Node
  
  2 HKEY_CURRENT_USER\Software\Classes\Wow6432Node
  
  3 HKEY_CURRENT_USER\Software\Wow6432Node
  
  4 HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node
  
  5 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
  
  6 HKEY_USERS\.DEFAULT\Software\Wow6432Node
  
  7 HKEY_USERS\S-1-5-18\Software\Wow6432Node
  
  8 HKEY_USERS\S-1-5-21-1963773873-535440688-1456871427-1000\Software\Classes\Wow6432Node
  
  9 HKEY_USERS\S-1-5-21-1963773873-535440688-1456871427-1000\Software\Wow6432Node
  
  10 HKEY_USERS\S-1-5-21-1963773873-535440688-1456871427-1000_Classes\Wow6432Node

A search with Registry Finder:
- 1 HKEY_CURRENT_USER\software\Wow6432Node\
  
  2 HKEY_LOCAL_MACHINE\software\Wow6432Node\

It seems Registry Finder is not comfortable yet with an X64 registry ...

tullik

jv16 wrote
...
tullik wrote

*** None of the file system Explore features work in any tool where I've tried them (a bug).

*** None of the “Open in RegEdit” features work in any tool where I've tried them (a bug).

Trying to fix these...

Good!

Without those, checking results on the x64 machine is very onerous.

tullik

tullik wrote
...
A search with Registry Finder:

1 HKEY_CURRENT_USER\software\Wow6432Node\

2 HKEY_LOCAL_MACHINE\software\Wow6432Node\

It seems Registry Finder is not comfortable yet with an X64 registry ...

Search word: Wow6432Node

Search only keys (all HKEY types)

Ignore words:

\Wow6432Node\a

\Wow6432Node\b

\Wow6432Node\c

\Wow6432Node\d

\Wow6432Node\e

\Wow6432Node\f

\Wow6432Node\g

\Wow6432Node\h

\Wow6432Node\i

\Wow6432Node\j

\Wow6432Node\k

\Wow6432Node\l

\Wow6432Node\m

\Wow6432Node\n

\Wow6432Node\o

\Wow6432Node\p

\Wow6432Node\q

\Wow6432Node\r

\Wow6432Node\s

\Wow6432Node\t

\Wow6432Node\u

\Wow6432Node\v

\Wow6432Node\w

\Wow6432Node\x

\Wow6432Node\y

\Wow6432Node\z

Results should show only the topmost Wow6432Node keys.

jv16

jv16 PowerTools 2010 test version 8 has been released to a group of 8 people for testing. There are still many rought edges and easy-to-spot bugs, I want to get all these fixed before the actual public beta testing begins.

« Previous Page Next Page »