jv16's development blog

tullik

Version 2.0.0.922, on an x64 Windows 7 desktop:

More new:

225. Registry Monitor: HKCC snapshot fails with “EassertionFailed” per the crash logger. Twice in a row. __ 922 x64 w7 (.)

*EassertionFailed.zip

jv16

tullik wrote

220. File Tool, Split: division by zero exception upon clicking “Simulate.” __ 922 x64 w7 (.)

I couldn't fix this yet, but I added more debug code to the feature, so please send the debug log and bugreport.txt the next time this happens and I'll be able to fix it.

tullik wrote

221. Automation tool: does not list a Registry Cleaner task. __ 922 x64 w7 (.)

Bug confirmed and fixed. The issue was caused by an incorrectly formatted file name, the file name given to the task was " Registry Cleaner (safest).jvb". It was the space character at the front that caused the issue.

Starting from the next released version, it's no longer possible to give such a name to an automation task, and the Automation Tool will also check for such incorrect names as well.

tullik

Sorry about cluttering your blog with so many 922 prerelease test results. :

Feel free to move my posts to a Beta 6 topic when there is one. 8)

Several (perhaps 10 to 20) prior issues that are in my testing log, but not in your change log, are gone with 922. They may be deduced from the tags in the "big list" here: http://www.macecraft.com/phpBB3/viewtopic.php?p=23201#p23201

Starting 7 May, I will be away for several weeks. I will have an x86 notebook, so I can download betas when I find an internet access point.

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.

tullik

jv16 wrote
... And FYI: I just found a bug from the Registry Cleaner Engine's duplicate data check, that caused the engine to check and recheck same pieces of data up to five times. This is the main reason why the Registry Cleaner has been so slow with the previous versions. We are now back on track with the speed.

After I confirmed initial setup did not freeze on my x86 desktop, I ran a most aggressive C & F M C.

It was way too slow, taking over 30 minutes at only 50% cpu. Further, it significantly degraded the response time of the entire desktop user interface (i. e., windows itself). Could the bug you mentioned have caused both these things?

jv16

tullik wrote
jv16 wrote... And FYI: I just found a bug from the Registry Cleaner Engine's duplicate data check, that caused the engine to check and recheck same pieces of data up to five times. This is the main reason why the Registry Cleaner has been so slow with the previous versions. We are now back on track with the speed.

After I confirmed initial setup did not freeze on my x86 desktop, I ran a most aggressive C & F M C.

It was way too slow, taking over 30 minutes at only 50% cpu. Further, it significantly degraded the response time of the entire desktop user interface (i. e., windows itself). Could the bug you mentioned have caused both these things?

I think so. But there is no need to guess, I sent you an updated Pre-Release version a few seconds ago, you can give it a quick try and let me know if the issue still exists.

siliconman01

This is on Windows 7 x64 Professional with PT V2.0.0.923.

The Registry Cleaner speed is back to normal and appears to functioning okay now on the most aggressive mode.

The Unit Testing tool is hanging and then crashing. The bugreport and debug log is attached.

I am getting frequent crashes when closing Jv16. It does not happen every time, but is frequent. The bugreport and debug is attached.

siliconman01

This is on Windows 7 x86 Professional with PT V2.0.0.923

Attached are logs of Unit Testing crashes.

tullik

jv16 wrote
... I think so. But there is no need to guess, I sent you an updated Pre-Release version a few seconds ago, you can give it a quick try and let me know if the issue still exists.

Version 2.0.0.923

On an x64 Windows 7 desktop; these were much faster:

Initial setup

C&FMC (most aggressive)

Registry Cleaner (most aggressive)

C&FMC found these:

*C&FMC (923) 1.JPG

Registry Cleaner found these:

*Reg Clnr (923) 1.JPG

The 15 vs. 8 difference was "Obsolete software entry" types. C&FMC shows a 64-bit view key in the list when the error was triggered by a 32-bit view key. It backs up the 32-bit view key. Registry Cleaner is not listing such items at all.

I'll try initial setup and C&FMC on the x86 Vista desktop later, to see if that answers my question.

212eta

I'd like to ask if the New jv16 PowerTools 2010

will include a Context (Right-Click) Menu

that will allow users to Securely Erase

Files, Folders, Shortcuts, Desktop Shortcuts etc.

with the known Erasing Methods (i.e. 3, 7, and 35 passes).

Erasing through the Context/Right-Click Menu is very useful!

tullik

jv16 wrote
... Also Tullik: if the problem still occurs with the File Split feature, please send over the debug logs and I should be able to fix it. ...

This APPCRASH also hung the crash logger, so there is no bugreport.txt.

*Split APPCRASH.zip

jv16

tullik wrote
jv16 wrote ... Also Tullik: if the problem still occurs with the File Split feature, please send over the debug logs and I should be able to fix it. ...

This APPCRASH also hung the crash logger, so there is no bugreport.txt.

*Split APPCRASH.zip

According to the log, you are trying to split one file. How you are trying to split it? That is, what settings are you using with the File Split tool?

tullik

jv16 wrote
... According to the log, you are trying to split one file. How you are trying to split it? That is, what settings are you using with the File Split tool?

Equally sized blocks: 4 AND "Generating a new filename"

I just did it again with the same outcome: APPCRASH upon clicking Start.

The former bug (division by zero upon clicking Simulate) is gone.

226. File Tool, Split: APPCRASH upon clicking “Start.” __ 923 x64 w7 (.)

tullik

tullik wrote
jv16 wrote... And FYI: I just found a bug from the Registry Cleaner Engine's duplicate data check, that caused the engine to check and recheck same pieces of data up to five times. This is the main reason why the Registry Cleaner has been so slow with the previous versions. We are now back on track with the speed.

After I confirmed initial setup did not freeze on my x86 desktop, I ran a most aggressive C & F M C.

It was way too slow, taking over 30 minutes at only 50% cpu. Further, it significantly degraded the response time of the entire desktop user interface (i. e., windows itself). Could the bug you mentioned have caused both these things?

On the x86 Vista desktop with version 2.0.0.923:

Initial setup: ~ 2 minutes

C&FMC (most aggressive): < 2 minutes

The windows desktop responded normally to all actions done

So, yes ...

redseujac

Jouni

As promised you find in attachment the log file concerning the Registry Compactor.

tullik

227. File Find and Replace results window : Button: Abort – not visible when populating the results list. (If that's where it is.) __ 923 x64 w7 (.)

228. File Find and Replace results window : Button: Abort2 – stays red when clicked during replace. __ 923 x64 w7 (.)

jv16

212eta wrote
I'd like to ask if the New jv16 PowerTools 2010

will include a Context (Right-Click) Menu

that will allow users to Securely Erase

Files, Folders, Shortcuts, Desktop Shortcuts etc.

with the known Erasing Methods (i.e. 3, 7, and 35 passes).

Erasing through the Context/Right-Click Menu is very useful!

PowerTools 2010 will not include such feature, I'm afraid. We have been thinking about features like these for a while, but I'm not sure if we want to take the step of integrating the program more to Windows.

jv16

tullik wrote

The former bug (division by zero upon clicking Simulate) is gone.

226. File Tool, Split: APPCRASH upon clicking “Start.” __ 923 x64 w7 (.)

This is now fixed, thanks for reporting!

I'll focus on the other issues found from the Pre-Release versions and after those are fixed, it's time to release the Beta6 to other beta testers as well.

tullik

tullik wrote
... Several (perhaps 10 to 20) prior issues that are in my testing log, but not in your change log, are gone with 922. They may be deduced from the tags in the "big list" here: http://www.macecraft.com/phpBB3/viewtopic.php?p=23201#p23201 ...

For example, with Firefox, a Find box containing |.| 922 will , one at a time using Next, highlight the testing log items closed by version 2.0.0.922.

212eta

jv16 wrote
212eta wroteI'd like to ask if the New jv16 PowerTools 2010

will include a Context (Right-Click) Menu

that will allow users to Securely Erase

Files, Folders, Shortcuts, Desktop Shortcuts etc.

with the known Erasing Methods (i.e. 3, 7, and 35 passes).

Erasing through the Context/Right-Click Menu is very useful!

PowerTools 2010 will not include such feature, I'm afraid. We have been thinking about features like these for a while, but I'm not sure if we want to take the step of integrating the program more to Windows.

jv16 PT is not just a Registry Cleaner; it is a Collection of Tools for System Maintenance.

I can't imagine a System Maintenance Suite without an Erasure Utility!

TuneUp Utilities and ACE Utilities have an Erasure Utility.

What a PITY... jv16 PT decided NOT to have one...

« Previous Page Next Page »