jv16 PowerTools 2010 RC1 (latest build: 961)

jv16

chefvisor wrote
Hallo there,

I can't download the jv16 PowerTools 2010 RC1,because my Norton Internet security tells me, the version is dangerous with a virus and busted the download.

The file is not dangerous. You'll have to wait for a day or two for Norton to fix the false detection in their software. Or download the software with Norton Internet Security disabled.

siliconman01

jv16 wrote
chefvisor wroteHallo there,

I can't download the jv16 PowerTools 2010 RC1,because my Norton Internet security tells me, the version is dangerous with a virus and busted the download.

The file is not dangerous. You'll have to wait for a day or two for Norton to fix the false detection in their software. Or download the software with Norton Internet Security disabled.

NIS 2011 Beta on Windows 7 x86 Professional says the RC1 download is safe. And Avira Premium Security Suite V10 on Windows 7 x64 Professional says it is safe.

leonardo

jv16 wrote
Leonardo wrote
jv16 wrote

Could you also post a Debug Log of this happening? Just in case I didn't catch the bug already. Thanks.

I attached two .zip files, with the Debug log + Screenshot of both the b944 and RC1 'Registry Cleaners' result lists.Hopefully this is what you wanted?

According to the Debug Log you only ran the Registry Cleaner. Could you please send a Debug Log that shows you running the Registry Cleaner and then trying the Fix or Delete buttons as long as you see the problem of nothing happening after a click?

I ran RC1 Registry Cleaner and in the Result window I played with the 'Fix' and 'Delete' buttons till the point that both 'Delete' and 'Fix' did not react anymore!

ADDED COMMENT:

I added a second test set from a clean start were the problem with the 'Fix' and 'Delete' buttons almost immediately started.

roving

Roving has sent the bugreport.txt by PM to jv16. Anything else needed?

roving

I just re-opened jv16 2010 RC1 from its desktop shortcut to work with the Debug feature. DEBUG no longer appears witH Files Language Tools and Help. I just checked and opening 2010 Beta7 948 still has Debug. What happened? Any clue how I can get it back? Sreenshot attached. Thanks, Roving

tullik

In the folder containing jv16PT.exe, create an empty file named DebugMode.dat. The next time you start the program, DEBUG mode will be back.

Apparently the developer decided not to make DEBUG mode the default in the Release Candidate.

jv16

tullik wrote
In the folder containing jv16PT.exe, create an empty file named DebugMode.dat. The next time you start the program, DEBUG mode will be back.

Apparently the developer decided not to make DEBUG mode the default in the Release Candidate.

You can also get the Debug Mode back by opening the program, pressing down Ctrl and Shift, and selecting "Enable debug mode" from the just appeared Debug menu.

The debug menu is no longer visible by default, because this is a Release Candidate. In other words, it's as close to the final version as possible, therefore all the debug features are turned off by default.

leonardo

jv16 wrote
tullik wroteIn the folder containing jv16PT.exe, create an empty file named DebugMode.dat. The next time you start the program, DEBUG mode will be back.

Apparently the developer decided not to make DEBUG mode the default in the Release Candidate.

You can also get the Debug Mode back by opening the program, pressing down Ctrl and Shift, and selecting "Enable debug mode" from the just appeared Debug menu.

The debug menu is no longer visible by default, because this is a Release Candidate. In other words, it's as close to the final version as possible, therefore all the debug features are turned off by default.

Perhaps you can imbed this usefull piece of information in "Please read the following before downloading" on the 1st page of this forum in the topic: "How to create a Debug Log"

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

Leonardo wrote

Perhaps you can imbed this usefull piece of information in "Please read the following before downloading" on the 1st page of this forum in the topic: "How to create a Debug Log"

Agreed & done.

leonardo

How about this difference in the result list of the 'Registry Cleaner'.

Is this by design? It started with b947!

See the attached screen shot, RC1 at the top and B947 at the bottom.

jv16

roving wrote
Roving has sent the bugreport.txt by PM to jv16. Anything else needed?

Thank you very much for sending the BugReport.txt! It allowed me to find and fix a previously undetected bug that occurs in a very special case of fixing a registry error. The issue is now fixed and a new build with this fix will be released shortly. Thank you again!

jv16

Leonardo wrote
How about this difference in the result list of the 'Registry Cleaner'.

Is this by design? It started with b947!

See the attached screen shot, RC1 at the top and B947 at the bottom.

This is due to toning down the aggressivity of the Registry Cleaner Engine, the current builds detect less errors than previous ones. Just to be safe. We'll bring back some more aggressivity in later builds.

jv16

Updated build 950 released:

http://www.macecraft.com/downloads/betas/jv16PT2010_RC1_b950.exe

Here is the Change Log:

Issues Fixed (since the original RC1 release) Issues found by beta testers (new numbers) 1. The new longer text message shown by Registry Compactor is unreadable because the text is cut by the popup box. 2. Clicking Fix or Delete in the Registry Cleaner can sometimes cause nothing to happen at all. 3. Using the Fix feature of PowerTools' Registry Cleaner can sometimes cause an Access Violation. This is a very rare issue and only happens when fixing a very specific type of registry error. 4. The Help > Check for Updates feature doesn't always work properly, it sometimes doesn't check for the latest version if used manually. Issues found in in-house testing (none so far) Improvements done (none so far)

Fixes in the making:

1. The Registry Cleaner freezes on some systems (mainly Windows XP) if run with the Reference Mode enabled.

2. PowerTools does not work well in systems with more than one display.

leonardo

XP-Pro-SP3 with RC1 build 950:

I ran Registry Cleaner and played a while with the 'Fix' and 'Delete' buttons in the result list:

1. I did not (yet) encounter a situation where the 'Fix' and 'Delete' buttons did not respond!

2. The warning message that is supposed to appear only on clicking the 'Delete' button, sometimes does NOT appear and sometimes appears on clicking the 'Fix' button.

3. Attached is the Debug Log of this test session.

rdtmk5

Just installed Build 950 Click Fix after running Registry Cleaner - still receiving a warning dialog that I am about to delete a lot erroneous registry data and that Fix is the better option. Again, this appears to be the Delete warning message.

rdtmk5

Follow-on to previous message. The erroneous Fix/Delete warning behavior seems to occur only when I select ALL identified registry errors for repair. If I select the errors 1 section at a time (i.e., Invalid file or directory reference, Obsolete software entry, etc.) and select Fix, the correct acknowledgment message appears and things appear to work normally.

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.

leonardo

jv16 wrote
Leonardo wroteHow about this difference in the result list of the 'Registry Cleaner'.

Is this by design? It started with b947!

See the attached screen shot, RC1 at the top and B947 at the bottom.

This is due to tuning down the aggressivity of the Registry Cleaner Engine, the current builds detect less errors than previous ones. Just to be safe. We'll bring back some more aggressivity in later builds.

For test purposes I compared the Registry Cleaner from jv16PT-2009-build 606 with jv16PT-2010-RC1 build 950.

The effect of tuning down the aggressivity is 'quite noticeable'.

See the attached screenshot: RC1 build 950 is at the top, 2009 build 606 is at the bottom.

siliconman01

Windows 7 x64 and Windows 7 x86 Professional.

Debug>Unit Test tool crashes with the same problem as has been posted on several previous builds. Is there any need to post the results or even test the tool at this point? I see no mention that it is a Known Issue. It seems to have fallen off the radar a few betas back.

« Previous Page Next Page »