In light of siliconman01's report, I will likely not do tests with my XP Pro SP3 notebook with this rendition of the program.
Private test build 569 released (and now finally 580)
Vista 64 sp2
redseujac wrotejepe wroteHello Jouni,
I found the following, tiny, anomalies by verifying my translation:
- 2) When switching from the language PT was started, to another one (English, French or Dutch), the Tool names in Tools menu don't switch to the new language, but stay in the language PT was started.
3) The header in the Settings-window "jv16 powerTools 2009 - Settings" stays in English, when changing the language.
Not fixed in build 575!
So...
- the Tool names language in Tools menu only changes after leaving the program and restarting it.
Could you please provide steps to reproduce the problem? I can't see it.
redseujac wrote- "Settings" caption in the Settings window can't be translated.
Confirmed and fixed!
tullik wroteredseujac wroteRegistry Cleaner > Advanced Options
. . .
- Automatically expand all the result categories does NOT show even with the English language selected.
That's OK.
PTLite has three levels in the structured list. PT2009 has just two levels.
This is correct, since PT 2009 only has two levels, only one of the expand options is needed and available.
redseujac wroteRegistry Cleaner > Advanced Options
- Automativally select all found items
- Automatically expand the main result categories
do not show in the options list when another language but English is choosen (though the expressions ARE translated).
I'm afraid I had to do a small change to the English.lng.
G_4DB = ||ÿ||Automatically remove all found erroneous data (NOT RECOMMENDED)||ÿ||Automatically fix all found erroneous data (NOT RECOMMENDED)||ÿ||Use as little CPU power as possible||ÿ||Don't show items that would be automatically re-created||ÿ||Don't pop up the window after finishing||ÿ||Don't show the Scan Report after finishing||ÿ||Automatically select all found items||ÿ||Automatically expand the main result categories||ÿ||
The two last items were added under
tullik wroteC:\hiberfil.sys still shows in red in the caption area. I suppose C:\pagefile.sys would also, but this PC's registry doesn't have the triggering entry.
Would it be possible to get a .reg file to reproduce the issue?
tullik wrote"Explore" is not in the context menu of an unselected line containing a file reference. It is also not there when the line is selected. However, the explore button in the caption area works properly.
Selected = box checked ...
This is by design, the Registry Cleaner does not provide the Explore Right-Click option, such option is only available with the file tools. I guess it would be logical to include, but I'd rather not do such change to the English.lng at the moment.
tullik wroteThe test case of HKEY_LOCAL_MACHINE\Software\classes\Bad item display\by jv16PT\in structured list\Subkey 2\c (for example) does not get the same treatment as in PTLite.
PTLite does it better.
Better how? I do not see any difference how the test key is displayed.
siliconman01 wroteOn Vista SP2 RTM x64 Business,
When doing a "Never Show Again" on 448 found items, an Internal Error RCRF-D-1b occurs. I am attaching the keys found during the scan and the SuperRegIgnore.dat file after the "Never Show Again" was performed.
I also emailed you a Debug log.
Thank you for the log! The issue now fixed.
siliconman01 wroteOn my XP-SP3, Build 575 will not install. The installer hangs on "Extracting Files" and the CPU goes to 100% utilized. The only way to get out of the problem is to hard boot the system.
This sounds like problem in the Installer file, not in PowerTools, so there is very little I can do about that. We use InnoSetup for the installer and usually it works very nicely.
siliconman01 wroteBefore I ran into this on my own XP-SP3 system, I stupidly emailed my brother and had him download/install Build 575 to see if his ISOFILE problem was fixed on his XP-SP3 system. It installed on his system. HOWEVER, when he ran a registry cleaning, the cleaner ran and at the end came up with a blank window for the key founds. The system then locked up. He could not close jv16 either via the X or End Process in the Task Manager. He could not shutdown or restart. So he hard booted. When the system restarted, the only thing he had was the desktop...none of his normal startup programs. We were able to recover with a system restore.
Do you mean the program crashed during scan, or after clicking the Fix button?
drob wroteRegistry cleaner in structured mode still freezes for me, using raw list works fine.
Vista 64 sp2
How long does the raw list mode take to run, and how long have you waited for the structured mode to run?
jv16 wrotetullik wroteC:\hiberfil.sys still shows in red in the caption area. I suppose C:\pagefile.sys would also, but this PC's registry doesn't have the triggering entry.Would it be possible to get a .reg file to reproduce the issue?
Here it is:
Windows Registry Editor Version 5.00
; File created by TBackupTool
; Component version: 1.4.2
; Component used by: jv16 PowerTools 2009
; Program version: 1.9.0.569
; File Description:
; Date: 09.05.2009
; Time: 19
"C:\\hiberfil.sys"="07/21/2008 10 PM"
"C:\\pagefile.sys"="07/21/2008 10 PM"
siliconman01 wrote:
On my XP-SP3, Build 575 will not install. The installer hangs on "Extracting Files" and the CPU goes to 100% utilized. The only way to get out of the problem is to hard boot the system.
This sounds like problem in the Installer file, not in PowerTools, so there is very little I can do about that. We use InnoSetup for the installer and usually it works very nicely.
B 569 re-installs fine. There is something wrong with B575. There are three XP machines in this thread that cannot use B575...me..my brother..and Boofo. These are all 32-bit machines.
siliconman01 wrote:
Before I ran into this on my own XP-SP3 system, I stupidly emailed my brother and had him download/install Build 575 to see if his ISOFILE problem was fixed on his XP-SP3 system. It installed on his system. HOWEVER, when he ran a registry cleaning, the cleaner ran and at the end came up with a blank window for the key founds. The system then locked up. He could not close jv16 either via the X or End Process in the Task Manager. He could not shutdown or restart. So he hard booted. When the system restarted, the only thing he had was the desktop...none of his normal startup programs. We were able to recover with a system restore.
Do you mean the program crashed during scan, or after clicking the Fix button?
At the end of the scan. Nothing worked in jv16 following that.
siliconman01 wrotejv16 wroteDo you mean the program crashed during scan, or after clicking the Fix button?
At the end of the scan. Nothing worked in jv16 following that.
In such case I do not see how PowerTools could have caused the problem with Windows, because during the scan everything works in read-only mode and PowerTools does not nor cannot change anything. But very strange indeed.
tullik wroteUsing the extended interface, I have five PTLite windows open. Four have the minimize button. Clicking that button in any of the four windows causes all five to minimize to the task bar.This behavior, reported for PTLite, now exists in PT2009 v.1.9.0.575.
It makes it very inconvenient for users who work with several PT windows open at the same time.
The prior behavior which minimized only chosen individual windows to the bottom of the screen was better. Having each window minimize to a unique task bar entry would be acceptable. What it does now in PT2009 (575) is not.
It's not a big issue with PTLite since, at most, only six different Macecraft windows for the main and subsidiary tasks can be open at the same time.
Will this be changed back, or will we have to again get used to an excessive dragging of windows around to see what's happening?