jv16 PowerTools 2007 Beta1 released

jv16

drob wrote
Two bugs found, one is in the file cleaner, even if i checked only my C drive, file cleaner would display results from D drive as well, interesting point, no other drive but checked C and unchecked D would be displayed even that there are other drives (E+). This issue was checked on two boxes an verified.

The drive selection is only used in some features of the tool, for example the search for Unused fonts, Unused shared DLL/OCX and the Listing of all Temp files ("List all files from the system temp dirs" feature) files always work no matter what drive settings are selected.

Are you certain none of these three features were checked when you ran the tool?

tullik

drob wrote
Two bugs found, one is in the file cleaner, even if i checked only my C drive, file cleaner would display results from D drive as well, interesting point, no other drive but checked C and unchecked D would be displayed even that there are other drives (E+). This issue was checked on two boxes an verified.

Second bug, a variation of the registry cleaner "abort" bug, when abort is clicked it will continue scanning and display an empty results window, it also requires a few clicks to become grayed out.

Regarding first bug: haven't tried to confirm yet. Will later (in Beta 2)-- there are several strange behaviors in that area.

Regarding second bug:

Running with a non-maximized window, Abort stopped the scan immediately (thread count disappeared and ": The File Cleaner is now finished. ..." appeared in the message box.

Running with a maximized window, Abort stopped the scan immediately (thread count disappeared). The "Size" and "Last modified" columns continued to fill in (desirable, not a bug). When the window was unmaximized, the message box was as above.

Possible conclusion: not a bug but a consequence of there being no screen room for the message box.

Question about "empty results window" -- were there any results in the window when you clicked "Abort?"

drob

@tullik: no no results to begin with.

@jv16: Once all those setting were removed, indeed only C drive was scanned, this should be clearer in the options, or better yet the drive setting should be enforced in all situations.

Regarding the abort issue, it takes anywhere from 1 to 5 clicks to get the abort grayed out, the first click reduces the number of running threads to 2 then after few more clicks it is down to 1, however after few seconds the backup prompt is displayed, if you click close immediately after the abort is grayed out and try relaunching the cleaner you get an error tool already running error. this is all done with NONE maximized window.

One more bug found, when creating an automation job for registry cleaner in aggressive mode, and running it, either via the manager or the desktop, the window just pops out and closes immediately, decreasing from aggressive mode, it runs properly. My guess is that this is due to the warning message not being displayed or clicked.

tullik

drob wrote
... Regarding the abort issue, it takes anywhere from 1 to 5 clicks to get the abort grayed out, the first click reduces the number of running threads to 2 then after few more clicks it is down to 1, however after few seconds the backup prompt is displayed, if you click close immediately after the abort is grayed out and try relaunching the cleaner you get an error tool already running error. this is all done with NONE maximized window. ...

That explains the different behavior -- I aborted during the initial scan.

You must have completed the initial scan, selected lines, then clicked Remove and Abort one right after the other ... ?

drob

@tullik:

No, but i run in fully automatic, which could explain the deferences. To make sure i just tested again in manual mode, and same issue however with a twist, clicking the abort grays it out and thread count is down to two, however after few seconds it ungrays out (if thats even a word) and clicking it again grays it out again and thread count is down to one. again if you click abort and close and immediately try to launch another instance of registry cleaner you get the already running error. so to summarize - hitting abort leaves some threads running.

blackdex

drob wrote
Second bug, a variation of the registry cleaner "abort" bug, when abort is clicked it will continue scanning and display an empty results window, it also requires a few clicks to become grayed out.

Confirmed here.

In my opinion, when pressing any abort button it should be greyd out, and then it should close any and all thread(s) left running and not trying to finish the running thread(s) with the whole scan.

But i don't know what PT's does currently.

tullik

File Cleaner bugs ... ?

FC settings:

1. Unneeded files, safe mode

2. More -- none checked

3. Options advanced -- none checked

4. Options drives
C:\ -WDC_boot (XP pro boot)

D:\ -Sea_boot (XP pro boot, selectable via bios change -- has Vista beta hung off it)

I:\ -WDC_vista -- the Vista beta

5. Ignore words: none

Result: (778 files on list) FC picks files out of the Recycle bins on D:\ and I:\ -- doesn't seem like a good idea -- should it be considered a bug?

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 to 4. As before

5. Ignore words: recycle

Result: (558 files on list) FC ignores the Recycle bins on D:\ and I:\ -- a workaround

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 to 5. as before, with "But only files which have not been accessed in the last 20 days" selected in 1. "Empty files" not checked.

Result: (23 files) all are in specified date range but all are zero bytes. All are a safe mode extension (*.tmp).

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 to 5. as before, with "But only files which have not been accessed in the last 20 days selected in 1. "Empty files" is checked.

Result: (1183 files) all are zero bytes -- apparently the "Empty files" option overrides "safe mode" -- is this a bug?

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

"But only files which have not been accessed in the last 20 days" and "Empty files" not checked is not picking up files in specified range if they have a non-zero size.

redseujac

drob wrote
...Second bug, a variation of the registry cleaner "abort" bug, when abort is clicked it will continue scanning ... it also requires a few clicks to become grayed out.

Confirmed also here (not running in "full automatic mode").

blackdex

Automation Tools - v1.7.0.356 - Bug

I created an Automated task that should run during System Start.

I selected it to Remove Files with File Cleaner, and that it should shutdown/exit PT's after it is done.

Now it couldn't remove some files with the File Cleaner, and that window stayed open. including an message/debug window of an other tool (Can't remember which tool it was).

PS: Haven't tryed to reproduce it. (Have to work on school stuff :( buzzy buzzy).

jv16

The new History Cleaner is now done. I'm currently working on fixing the problems of the Disk Defragmenter. There were two bugs in the defragmentation engine, this caused the tool not to not being able to defrag some drives.

There is still one known bug in the defrag engine which decreases the performance of the tool, but it should now be working better.

Beta2 was scheduled to be released on this week, but I'm afraid it will be delayed. It will be released on next week.

It contains fixes to some 30+ most obvious bugs (read: the ones which were easy to fix). The main emphasis has been on making the new features (One Click Cleaner and Disk Defragmenter) work as they should, as well as on the improvements of some tools (History/MRU Cleaner and Start Menu Fixer).

The main bug fixing phase starts after Beta2, then all reported bugs should be fixed.

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.

redseujac

When I run File Cleaner and/or 1 Click Cleaner to clean (among others) the Temporary Internetfiles directory, I always get the message:

Error! Failed to remove D:\Temporary Internet Files\Content.IE5\index.dat

Well, it's my opinion that a "well-reputed" file cleaner should (must) be able to clear those famous "index.dat" files.

Actually the indicated tools can't do the job, while I am convinced (certainly as many other users) they should/must be able to do it!

PCMesh Internet Cleanup and CCleaner can do it, why should/could jv16PT2007 not be able to manage :

It's well understood that each time the computer has to be rebooted before those files are really cleared.

Conclusion: I suggest strongly jv16 to add that feature to the PowerTools 2007 :

PS: if the feature is actually in the PT (never noticed that), well then I'm stupid as could be :

redseujac

When running Registry Cleaner and scanning and fixing/removing the erroneous entries is done, it happens frequently the whole process was not able to remove some/many entries from the registry because access to those entries is/was denied by Windows, mostly due to lack of necessary permissions.

Actually the user doesn't know/see those entries :

It should be nice and very useful if - after the whole process of scanning and fixing/removing - a (new) message warns the poor user like this:

"Some entries couldn't be removed from the registry. See the "CouldNotRemove.txt" logfile in the jv16 PowerTools 2007 main folder for more details."

Naturally a txt-logfile should be automatically made in the main folder of the program - with name as indicated above - containing all the entries which couldn't be removed from the registry, so the user - using Notepad - could see them and using Regedit could take the required measures ("permissions"?) to try letting the Registry Cleaner fix/remove them in a subsequent run.

Notice that Ray Geide's RegVac Registry Cleaner has already such a feature and I can confirm it's very very usefull :

sofabuddy

Greetings,

I just installed jv16 PowerTools 2007 Beta1 (in a different directory than jv16 PT2006) and could not get the app to run. I received the follwoing error:

"Your trial period has ended. Please, visit macecraft.com if you wish to purchase a license and continue to use this product. Contact support@macecraft.com if you have already purchased a license."

Has anyone else encountered this problem as well?

I searched the topic before I posted this, but found nothing.

PS: jv16 PT2006 works fine.

evest

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

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

This feature has now been included to the most features of PT 2007. The registry keys/entries that can't be modified/removed are listed in the Message Window feature, or shown in Windows dialogs if user has selected that messaging option.

If the API returns a reason code, will that be included in the message ... ?

jv16

tullik wrote

If the API returns a reason code, will that be included in the message ... ?

Yes, the API always returns a status code. If everything works out, it returns 0, if it returns anything else the returned code is the error code. This error code is displayed in PT 2007 starting from Beta2.

Similar system will most likely to be implemented to file removal procedures as well before the final release of PT 2007.

redseujac

jv16 wrote
...This feature has now been included to the most features of PT 2007. The registry keys/entries that can't be modified/removed are listed in the Message Window feature, or shown in Windows dialogs if user has selected that messaging option.

Thanks, jv16, but the disadvantages of showing the keys/entries in the Message Window vs. creating a txt-file in the main program directory are obvious: 1) the message can become rather/very long 2)one can not print the list with the keys as easily as they are enclosed in a text-file which can be opened/printed with Notepad 3)the message with the list is volatile while a txt-file is not.

jv16

redseujac wrote

Thanks, jv16, but the disadvantages of showing the keys/entries in the Message Window vs. creating a txt-file in the main program directory are obvious: 1) the message can become rather/very long 2)one can not print the list with the keys as easily as they are enclosed in a text-file which can be opened/printed with Notepad 3)the message with the list is volatile while a txt-file is not.

1) The Message Windows perform word wrapping and can be resized, just like Notepad.

2) The Message Window system in Beta2 and later contains a built-in support for printing, saving the data to file and copying it to clipboard. That is, pretty much everything you can do with Notepad.

3) I don't quite understand what you mean by the Message Windows being volatile.

Text files will not be used because it's not a very common practice to do so in Windows or in PowerTools. Text files are good for logging and storing settings, not to display data.

« Previous Page Next Page »