Test version 1.9.0.581 released (and now: 590)

doogie

Using build 588 shows Registry keys with incorrect permissions or owner. I don't believe these entries are incorrect.

They all relate to games and fixing them destroys any saved game data. Merging the backup does not correct this either.

Running Vista x64

jv16

redseujac wrote
Registry Finder / File Finder / probably all tools

Message "At least one search argument..."

After changing the focus on e.g. the Options tab, when you click on the blue link in the message window nothing happens.

I did a test and this issue applies probably to all such messages in every tool: the blue links don't work.

Confirmed and fixed.

File Finder

In the Error Message "At least one...", the possibilities "Search by contents" and "Search by owner" are missing.

Confirmed. I changed the wording to "At least one search argument, you can use for example Search by ..." This way we don't need to list every single option. This is important because in PowerTools 2010 there will be two different GUI's, one for beginners and one for advanced users. And both GUIs have a different set of tabs for each tool.

jv16

DooGie wrote
Using build 588 shows Registry keys with incorrect permissions or owner. I don't believe these entries are incorrect.

They all relate to games and fixing them destroys any saved game data. Merging the backup does not correct this either.

Running Vista x64

To be clear, did you use the Fix or the Delete button? And did you use the Structured registry results view (default) or the old raw list mode?

jv16

tullik wrote
jv16 wroteCan anyone confirm any remaining issues in the latest test version (build 588)?

I did a "quick and dirty" test of this issue: http://www.macecraft.com/bugtracker/bug/111243/

The fix is not working.

That is, the first PT task started still ends abruptly when the second PT task ends.

I believe I have now found and fixed the problem. A new test version will be released soon, and the official version will shortly follow.

jv16

siliconman01 wrote
siliconman01 wrote
siliconman01 wroteOn Vista SP2 x64, following a scan in the Registry Cleaner at top menu under File, the "Save list as" does nothing.

My apologies if this has been reported as a bug in bug tracker and is waiting to be fixed.

I submitted a BugTracker report on this because it does not work on the V1.9.0.580 either for x64 systems. Works fine on XP-SP3 x86 and Windows 7 RC 7100 x86.

This is the only issue that I see .... and only on x64.

I'm afraid this bug will most likely be fixed in PT 2010. The next product version uniforms all data listing windows of the program. Now there are four different data listing components which all require their own data saving, displaying and priting code. In PT 2010 there will be only be one listing component, the one developed for the structured list of PT 2009's Registry Cleaner.

jv16

A new test version released, please see the first message of the thread for the download link.

If nothing major is not found, this version will be released officially tomorrow. There are some remaining issues but the list of already fixed bugs is quite long, so this will be a good 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

jv16 wrote
... In PT 2010 there will be only be one listing component, the one developed for the structured list of PT 2009's Registry Cleaner.

Does that mean that, in none of the lists, will we be able to do a quick column re-size with a double click at a column header margin?

jv16

tullik wrote
jv16 wrote ... In PT 2010 there will be only be one listing component, the one developed for the structured list of PT 2009's Registry Cleaner.

Does that mean that, in none of the lists, will we be able to do a quick column re-size with a double click at a column header margin?

I'm afraid I don't quite understand?

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

jv16 wrote
tullik wrote
jv16 wrote ... In PT 2010 there will be only be one listing component, the one developed for the structured list of PT 2009's Registry Cleaner.

Does that mean that, in none of the lists, will we be able to do a quick column re-size with a double click at a column header margin?

I'm afraid I don't quite understand?

When I do a double click at a column header margin in the structured list of PT 2009's Registry Cleaner, it does not expand or contract that column's width as it does in the other PT lists.

Instead, it sorts the column (sometimes) or does nothing (usually).

tullik

You have probably already noticed this:

When you run the 590 "jv16 PowerTools," the windows task bar shows it as "PowerTools Lite."

siliconman01

tullik wrote
You have probably already noticed this:

When you run the 590 "jv16 PowerTools," the windows task bar shows it as "PowerTools Lite."

Yes, it surely does.

Other than that, I am seeing no new issues in 590 on Vista x64.

doogie

jv16 wrote
DooGie wroteUsing build 588 shows Registry keys with incorrect permissions or owner. I don't believe these entries are incorrect.

They all relate to games and fixing them destroys any saved game data. Merging the backup does not correct this either.

Running Vista x64

To be clear, did you use the Fix or the Delete button? And did you use the Structured registry results view (default) or the old raw list mode?

I used the Fix button and also the Structured registry results view.

mrcs

tullik wrote
Does that mean that, in none of the lists, will we be able to do a quick column re-size with a double click at a column header margin?

Gee, I hope not. I noticed that a long time ago the one time I used the Structured View rather than the Raw, which is my preference. I hope that view is not going away.

P.S. - I just tried the Structured View on 590 and it seems as though column re-size at column header margin is not available. It also seems from the message when changing to Raw view that it is going to be discontinued. The message says "performance is not as good" (not sure why that would be) under the Raw view.

tullik

I'm posting this here for reference by a bug report.

Submitted for PTLite v.1.9.0.589 on 8/7/2009

A one time (?) anomaly cleaning certain Registry Errors?

Caused by an undetected bug in PT2009 "Fix?"

No attachments.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Edit: a conclusion is at the end of the post ...

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The first run cleaned and backed up MRU/History stuff, temporary files, and temporary internet files with no apparent issues.

Then, using the same scan list, it cleaned and backed up six "Registry Errors." However, the program experienced an APPCRASH (see below). I restored the errors and ran another scan. That time, it cleaned and backed up the same six "Registry Errors," but no APPCRASH happened.

The "Registry Errors" backup file is a little strange. Namely, the four interspersed "c:\\- garbage\\desktop\\531\\jv16pt.exe"=- lines. There were no such items in the results list.

Windows Registry Editor Version 5.00


	
; File created by TBackupTool	
; Component version: 1.4.2	
; Component used by: PowerTools Lite	
; Program version: 1.9.0.589	
; File Description: *0 (PTL) Registry Errors	
; Date: 07.08.2009	
; Time: 01	
	
	
	
c:\\- garbage\\desktop\\531\\jv16pt.exe=-	
C:\\PROGRAM FILES\\MACECRAFT\\V\\Y-betas\\JV16 POWERTOOLS 2009 (582)\\jv16PT.exe="07/29/2009 8 AM"	
C:\\PROGRAM FILES\\MACECRAFT\\V\\Y-betas\\JV16PT_SETUP_HB_1.9.0.582.EXE="07/29/2009 7 AM"	
c:\\- garbage\\desktop\\531\\jv16pt.exe=-	
C:\\PROGRAM FILES\\MACECRAFT\\V\\Y-betas\\JV16 POWERTOOLS 2009 (581)\\jv16PT.exe="07/28/2009 10 AM"	
c:\\- garbage\\desktop\\531\\jv16pt.exe=-	
C:\\PROGRAM FILES\\MACECRAFT\\V\\Y-betas\\JV16 POWERTOOLS 2009 (585)\\jv16PT.exe="08/01/2009 10 AM"	
C:\\PROGRAM FILES\\MACECRAFT\\V\\Y-betas\\JV16PT_SETUP_HB_1.9.0.585.EXE="08/01/2009 10 AM"	
c:\\- garbage\\desktop\\531\\jv16pt.exe=-	
C:\\PROGRAM FILES\\MACECRAFT\\V\\Y-betas\\JV16 POWERTOOLS 2009 (584)\\jv16PT.exe="07/31/2009 10 AM"

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Product

jv16 PowerTools

Problem

Stopped working

Date

8/7/2009 1

Status

Not Reported

Problem signature

Problem Event Name: APPCRASH

Application Name: PTLite.exe

Application Version: 1.9.0.589

Application Timestamp: 2a425e19

Fault Module Name: kernel32.dll

Fault Module Version: 6.0.6000.16820

Fault Module Timestamp: 49952034

Exception Code: c0000005

Exception Offset: 0004fcac

OS Version: 6.0.6000.2.0.0.256.6

Locale ID: 1033

Additional Information 1: b37c

Additional Information 2: 2a7328d8bb40c81c93b4b5f46adb8e10

Additional Information 3: b37c

Additional Information 4: 2a7328d8bb40c81c93b4b5f46adb8e10

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Edit: I repeated the PTLite test with a RegEdit window open on the HKEY_CURRENT_USER\Software\BillP Studios\Detected\ActiveTasks key.

"Fix" changed all six errors to this name: c:\- garbage\desktop\531\jv16pt.exe which does exist and shows in FileCache.dat.

Since the registry does not support duplicate names under the same key, the six "fixes" resulted in a single named item, with the data of just one of them.

Conclusion: there is indeed a "Fix" (and backup) bug in PTLite (and therefore, in PT2009).

This particular key is only for history tracking, so there is no real harm in this case ...

Note: the APPCRASH is probably not related to this bug ... it did not happen again in subsequent tests.

jv16

tullik wrote

When I do a double click at a column header margin in the structured list of PT 2009's Registry Cleaner, it does not expand or contract that column's width as it does in the other PT lists.

Instead, it sorts the column (sometimes) or does nothing (usually).

I wasn't even aware of such feature. Well, if such feature is requested, it can be added to the new listing component as well. The nice thing is that when we use the new, custom developed listing component we can have what ever features we want.

tullik

Please consider this a request. :

The feature has been present in the lists since v.1.4.1.x (the first one I bought). It (along with the drag-resize feature) is very handy since the column width requirements do vary depending on what a scan finds.

I wouldn't be sorry, however, if the periodic dynamic column resizing that occurs with some tools, while they run, went away. IMO, that's more an annoyance than a help.

jv16

tullik wrote
You have probably already noticed this:

When you run the 590 "jv16 PowerTools," the windows task bar shows it as "PowerTools Lite."

Yep, confirmed and fixed.

jv16

tullik wrote

The "Registry Errors" backup file is a little strange. Namely, the four interspersed "c:\\- garbage\\desktop\\531\\jv16pt.exe"=- lines. There were no such items in the results list.

The line above means that if an entry of that name exists, it will be removed by the backup file (.reg).

tullik wrote

"Fix" changed all six errors to this name: c:\- garbage\desktop\531\jv16pt.exe which does exist and shows in FileCache.dat.

Since the registry does not support duplicate names under the same key, the six "fixes" resulted in a single named item, with the data of just one of them.

I have been thinking about this very problem earlier but I did not come up with any other solution in fixing an invalid file reference in a case like this. Gladly, this kind of cases of registry data are rare, so this is mainly a theoretical problem.

But still, in your opinion, how should cases like these be fixed?

« Previous Page Next Page »