PowerTools Lite RC1

jv16

DooGie wrote

More problematic in Windows 7 is the fact that any Invalid file or directory references do not get fixed or deleted. All other sections work fine apart from this one.

Can someone else confirm? Also, is this issue specific to Windows 7 or not?

redseujac

I used the extended UI with the settings at "More aggressive".

Then I switched to the simple UI and when clicking "Clean and fix..." I got the warning message about using the aggressive mode.

In the simple UI you can not change that because you can't access the scan settings, so you have to abort.

So, after switching from the extended UI to the simple UI the settings are kept as they were before.

Question: shouldn't it be better to return automatically to the default normal setting when the user switches from the extended to the simple UI, or is the actual situation by design, i.e. the settings choosen in the extended UI are kept when switching to the simple UI? Maybe that's easy for the advanced user who previously chooses his settings in the extended UI and then switches to the simple UI so he has afterwards only have to click on "Clean and fix..." to start immediately the cleaning mode he prefers.

jv16

tullik wrote
The explore button (...) in the caption area for a file does not do anything. Explore in the file's context menu works properly (i.e., the folder is opened).

You are correct, this bug is now also fixed.

jv16

tullik wrote
Registry items in MRU and History Data do not have Open in RegEdit in the context menu.

This is by design because some MRU and History Data items do not have registry entries, some have only files. And to show RegEdit option for some and for some not would be confusing, I think.

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

redseujac wrote
I

Question: shouldn't it be better to return automatically to the default normal setting when the user switches from the extended to the simple UI, or is the actual situation by design, i.e. the settings choosen in the extended UI are kept when switching to the simple UI? Maybe that's easy for the advanced user who previously chooses his settings in the extended UI and then switches to the simple UI so he has afterwards only have to click on "Clean and fix..." to start immediately the cleaning mode he prefers.

I gave this question lots of thinking and I came to the same idea as you: some advanced users might want to use the extended GUI mode to define the scan to work as they want, and then switch to simple mode in order to always start the scan with just one click, using the settings they want.

redseujac

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

FYI: I released an updated version with all the fixes mentioned above, the new version is available via the Help menu's Check For Updates feature. The program should also automatically prompt you about the new version.

redseujac

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

jv16 wrote
DooGie wrote

More problematic in Windows 7 is the fact that any Invalid file or directory references do not get fixed or deleted. All other sections work fine apart from this one.

Can someone else confirm? Also, is this issue specific to Windows 7 or not?

In my case it is specific to Windows 7 x64.

In Vista x64 it behaves as it should and either fixes or deletes the invalid entries.

jv16

redseujac wrote

Is the developer able to fix it, please?

Could you please start the program in Debug Mode, and from the Debug Log (after you have started the Scan) check what does it say after:

EasyFixForm.StartFileCleaner TempDirs=

This list contains all the directories the program has detected to be system's temp dirs.

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.

jepe

Hello,

After installing RC1b I can't see anymore the Language menu : - all the languages installed.

In RC1 it is present.

I am running under XP/SP3.

Jean-Paul

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.

redseujac

jv16 wrote
...

Could you please start the program in Debug Mode, and from the Debug Log (after you have started the Scan) check what does it say after:

EasyFixForm.StartFileCleaner TempDirs=

This list contains all the directories the program has detected to be system's temp dirs.

Unfortunately exactly what I feared: it founds only the following folders:

C:\Program Data\TEMP

C:\Temp

C:\Windows\Temp

EasyFixForm.StartFileCleaner TempDirs=C:\ProgramData\TEMP\ C:\Temp\ C:\Windows\Temp\

My actual Temp folders = E:\XX\Temp and E:\XX\Tijdelijke Internetbestanden (dutch for E:\XX\Temporary Internet Files)

Strange enough look at this in the debug.log

TempDir=E:\XX\TEMP\jv16PT_2009\ (E:\XX\TEMP, being the correct Temp files folder)!

Edit: Look at this post.

tullik

jv16 wrote
tullik wroteRegistry items in MRU and History Data do not have Open in RegEdit in the context menu.

This is by design because some MRU and History Data items do not have registry entries, some have only files. And to show RegEdit option for some and for some not would be confusing, I think.

I think a user who can't tell a file from a registry entry is already too confused …

I found the two highlighted items below worth checking ...

Without an Open in RegEdit option somewhere (context menu or caption area), it is not possible to easily see what the items represent. Even using a RegEdit search, after Start-->Run-->RegEdit, would be a problem, since what is shown provides no reliable information for what to use for the search.

It turns out the lines represent the Name and ID entry names for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectDraw\MostRecentApplication -- who would have guessed?

05-08-2009_12-15-24.jpg

jepe

Helo Jouni,

jv16 wrote

Do you have any updated translations installed? I.e. translations whose Header contains:

ProgDef = jv16/PTLite

The previous beta versions listed also the not-valid translations.

Yes, there is the Dutch translation for PT Lite. I deleted all other translations, so only English and Dutch are left ... no Language menu comes up.

Best regards

Jean-Paul

redseujac

Continuation of this post.

Sorry, I think I have found it and it seems to be my fault :

In FileCache.dat I had changed E = True in E = False and E:\XX\Temp is my actual Temp files folder... so...

When I changed it again in E = True, the temp files are listed

But... the Temporary Internet Files aren't shown yet and that remains an issue :

Conclusion: for the program being able to find Temp files the folder containing those Temp files may not be excluded from the FileCache.dat file, i.e. you may NOT put " = False.

redseujac

jepe wrote
Helo Jouni,

jv16 wrote

Do you have any updated translations installed? I.e. translations whose Header contains:

ProgDef = jv16/PTLite

The previous beta versions listed also the not-valid translations.

Yes, there is the Dutch translation for PT Lite. I deleted all other translations, so only English and Dutch are left ... no Language menu comes up.

Best regards

Jean-Paul

Confirmed! Jepe IS right: Translations are NOT showing in the Menu, though my Dutch translation is up-to-date and the header contains the right ProgDef. I also changed for testing that header in the French translation. Nothing to do: no "Translations" in Menu.

That issue should be fixed!

jv16

redseujac wrote

Confirmed! Jepe IS right: Translations are NOT showing in the Menu, though my Dutch translation is up-to-date and the header contains the right ProgDef. I also changed for testing that header in the French translation. Nothing to do: no "Translations" in Menu.

That issue should be fixed!

This is indeed a bug and I just noticed and fixed it myself. No language menu is shown if only two translations exist (e.g. English and Dutch), it is shown if three or more valid translations are found. The fix was included to the just-updated jv16 PowerTools and it will also be included to the next released version of PT Lite.

« Previous Page Next Page »