Part of the funny behavior of windows in PT 2007 beta2 is probably due to changes gone bad that were attempting to address this item first reported by wilbertnl. For instance, in Registry Cleaner, if you maximize the results window, PT forces it back to the last non-maximized size, I presume to show the message box.


The suggestion by wilbertnl here and agreed to by tullik here might be a better approach.


This beta1 workaround for Registry Cleaner still works in beta2 and avoids at least some of the funny behavior of windows in PT 2007 beta2.

tullik wrote
... Resize the results window so it occupies most of the top of the screen, leaving the bottom part for the message box ... PT remembers your last resizing of the results window.

When running Registry Finder or File Finder (for example), sometimes I see in the still developing results window, the items I am seeking. It would be desirable to stop the scan while leaving the results window up for closer examination. The Close button (which does the same thing as the upper right X widget) does not permit any examination since it immediately throws away the results window.


The new Abort button on the progress bar keeps the results window up. Unfortunately, if you have the Setting "Don't show the status indicator" so it won't get in the way when browsing/sorting the developing list, you also don't have the Abort (or Stop?) button.


Suggestion: take the Abort button off the progress bar (for those tools where it makes sense) and instead toggle Close to Abort (or Stop) while the scan is in progress.


If you really need/want to "Close" the in progress scan and throw away the results window, you still could click the X widget.

I noticed that the "Open in RegEdit Ctrl+R" option for some History/MRU Cleaner lines does nothing. Could these be registry items detected by the heuristic analyzer? Files? Both?


In any case, I am reluctant to test "Clearing" whatever these items are until I create a Restore Point ... and have access to a backup computer. Right now, I'm driving a few thousand miles and only have my laptop ...

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.
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.

Tarun wrote

x Files Left: 30


Is the x intentional for the titlebar when defragging?

Yes, this is debug code. There's a lot of similar debug messages in the program.


The File Left number shows the number of fragmented files left for the defragmenter to process. When the File Left number goes to 0 the process is completed.

tullik wrote
I noticed that the "Open in RegEdit Ctrl+R" option for some History/MRU Cleaner lines does nothing. Could these be registry items detected by the heuristic analyzer? Files? Both?

These are history data that are stored in file(s). I'll improve this functionality somehow.

Have you tried the new Disk Defragmenter? Does it work, and how long time does it take to complete? After it has completed, does the drive fragmentation per cent decreased?


It's working quite well on all the test systems I have tried it on. The main problem seems to be that the feature is rather slow on large disks with very little free space.

I installed Beta two but the update does not work. When you first install it it acts like it is checking for updates but does nothing. You can not tell it is working at all. This is the same result whtn you cleck "Check of update".


I have uninstalled and reinstalled with no difference.


Is it deactivated in beta 2?

The beta two leaves a place marker on the task bar even after the program has closed.

kbtarl wrote
I installed Beta two but the update does not work. When you first install it it acts like it is checking for updates but does nothing. You can not tell it is working at all. This is the same result whtn you cleck "Check of update".


I have uninstalled and reinstalled with no difference.


Is it deactivated in beta 2?

I guess so because it's a beta ... there are no possible upgrades.

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.

I'm finding that even with multiple passes, it does not fully defragment.

So I started DFF about 20 hours ago, and just left it alone. Message says "This might take a while..." After 20 hours it is still running. Says it;s checked about 101,200 files and is still cranking. Is this conceivable?


Larry@lynn.nt

Tarun wrote
I'm finding that even with multiple passes, it does not fully defragment.

This is a known problem. What I'm interested to know is how much does it defrag, i.e. what was the fragmentation per cent before and after you ran it.

Drive C:

: Runtime: 29.69

: Runtime: 1989.81


Drive D:

: Runtime: 56.47

: Runtime: 240.42


I've run it once since my screenshot yesterday, and the change was from 19.41% on drive C, to 19.20% on drive C.


Unfortunately I did not notice what the percentages were yesterday before and after the defrags.

jv16 wrote
tullik wroteI noticed that the "Open in RegEdit Ctrl+R" option for some History/MRU Cleaner lines does nothing. Could these be registry items detected by the heuristic analyzer? Files? Both?

These are history data that are stored in file(s). I'll improve this functionality somehow.

How about having the context menu for a line of this type invoke win explorer for the directory containing the file(s)?l

The context menu for all line types in the History/MRU Cleaner needs a "Never show again" option.


The warning message correctly says that the user may not want to remove some Recent Files items, for example.


One could use the "Never show again" option to protect such items, especially if one intends later to use the One Click Cleaner to remove history routinely ...

As posted previously, I've been unable to get passed the messagebox stating that my license has expired with both Beta 1 and Beta 2.


What troubles me, besides not being able to work any issues with either beta, is that I have a valid license for jv16 PT2006 on my system, and that version works without a hitch.


jv16, do you have any suggestions for me?


sb

Four items noted upon initial Beta2 installation:


Quick Tutorial: 2nd bullet, 1st screen, is grammatically incorrect (run-on sentence). "The product contains an amazing set of features, there is no need to master them all, you can use only the features you find useful." Suggest: "The product contains an amazing set of features. There is no need to master them all; you can use only the features you find useful."


Quick Tutorial: On cache generation page, after selection of "Generate the file cache now (Highly recommended)" check box, text reads, "The cache generation analyzes all of your system's hard drives, it can take a few minutes to complete." This is grammatically incorrect (run-on sentence). Suggest: "Since the cache generation analyzes all of your system's hard drives, it can take a few minutes to complete." or "The cache generation analyzes all of your system's hard drives, so it can take a few minutes to complete."


Quick Tutorial: Also on cache generation page, last sentence states, "The feature doesn't use the Internet and doesn't send the data to anyone." Upon clicking the Next button (after selecting the "Generate the file cache now (Highly recommended)" check box), a message box appears stating, "This feature requires jv16 Power Tools to connect to Macecraft Software's central server to download the information. No information is sent to Macecraft Software." The first sentence in the message box contradicts the sentence cited on the Quick Tutorial screen.


Also, Help options that open a browser window (e.g., Homepage..., Visit the online support forums, Search the web..., etc.) open Internet Explorer instead of the user's default browser.