jv16 PowerTools 2007 Beta3 released

jv16

jv16 PowerTools 2007 Beta3 is now released, you can download it from:

http://www.macecraft.com/downloads/betas/jv16pt_setup_2007_Beta3.exe

(if the link doesn't work, it means the beta testing for this version has already ended)

Warning

Do not install this program over any previous version of jv16 PowerTools, always install beta versions to a new directory. This product version is not an official release, it will contain bugs and can cause harm to your computer. Do not download or install this program unless you are willing to take the risk and understand what beta testing means.

On Beta Testing

All beta testers who submit valuable feedback, such as bug reports, performance reports, improvement ideas etc, will receive a free personal license for the product after it has been officially released. Simply installing and testing the application doesn't mean that you would automatically receive a free license, free licenses are issued only to those who submit valuable feedback.

General Release Notes

* Do not start to translate the English.lng yet, the language interface will still change.

* This version still lacks a few new icons (for example to the new One Click Cleaner).

* This version does not run under any Win9x system, such as Windows 95, 98, 98 SE nor ME. The program doesn't start due to a missing NT-only DLL file.

* The Beta3 contains a new trial system, it should allow you to test the program even if you have once used your free trial on any previous versions of jv16 PowerTools. The trial system has been heavily modified, therefore there might be minor bugs in it.

* The Disk Defragmenter doesn't yet work very well, this is a known problem and it will be addressed in Beta4.

Changes since Beta2

* Dozens of bugs fixed

* Improved Registry Cleaner's user interface

* File Cleaner's user interface heavily improved

Development schedule

RC1 (Release Candidate 1) version is expected to be released after 3-5 beta versions, the final version should be ready after 1-3 RC's.

Please send all your feedback and bug reports to this thread (use the Post Reply button).

Thank you very much.

PS. If you have too much free time on your hands, feel free to edit http://en.wikipedia.org/wiki/Macecraft_Software (discussion of Macecraft Software in Wikipedia is located in: http://www.macecraft.com/phpBB2/viewtopic.php?t=1739)

evest

History/MRU Cleaner

Appears to be broken (fresh installed to another folder). It hangs immediately after starting, no progress on the bar. The program can be stopped and closed, it just doesn't actually work. :

Trial Period, Activation, etc

The new system is fixed, it's not saying the trail period has ended (CMOS resets were messing with Beta2 for me).

File Tool

Mass splitting 50 RAR files results in the process failing to respond. 1mb blocks, Delete files after split, default naming policy, no simulation attempted.

The same process again with 15 mp3s resulted in nothing happening on the first attempt. The debug log showed "Done!", but no change to the files or folder occurred. A second attempt with the same settings resulted in something different altogether. Perhaps I'm misunderstanding the process of how this works, but the result was 122 Part## of the first track, and then remaining 14 tracks with no difference in filename or the file itself. The others still play, so they were unchanged despite being selected initially. Merging the 122 files rebuilds track 1, but the filename doesn't maintain it's original capitalizations, and has an added part at the end. Maybe this is working as its intended and I'm just trying too many things at once :)

Automation

Automation features that I use seem to be working as they should now, since my initial report in Beta1, excluding the History/MRU cleaner bug.

Debug Window

The debug window remains open after the program is closed, which I think is intended, but often when I close it, jv16PT.exe remains active in my processes list. I haven't had much luck reproducing it specifically, it's rather hit or miss, so it may not be the debug window causing this at all.

mod

Installation of Beta 3 successful on Vista 32 RTM

Cache update (initial) took 41 mins to complete (I have 13 drives, approx 510k files).

I do not remember any of the previous installations (XP SP2) taking more than a few minutes - less than 5. I had smaller HDDs then, but more logical drives.

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.

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

evest wrote

I'm currently editing my initial post in this thread with new bugs as I come across them, once this thread grows to a second page I'll start a new post there. Is that troublesome for you, or would doing it differently make it easier for you to sort through our reports?

It's a good idea to edit one's post and write all the comments to one post as long as you do it in a relatively short time period, it's not a good idea to edit posts to add new bug reports after many days.

If the message gets very long then it's better to divide it to multiple messages.

guizop

I gave a lot of files to check with duplicate file finder.

I use taskinfo to see what powertools is doing.

I had a full scan of all directories - Normal.

After this, PowerTools uses 90% of kernel CPU, 10% of user CPU, and opens sometimes a file, always in the same directory.

It has been running for more than 2 hours, with a sempron 3100+.

Since all the opened files belong to the same directory, I strongly suspect a bug.

drob

Automated regcleaner, again wont run in aggressive mode, opens and immediately closes, if set to not aggressive-runs correctly.

Duplicate finder, still wont accept DVD drive "Directory "H:\" does not exist".

hsavage

After running and closing the window jv16 Beta3 won't remove itself from memory, have to stop it using 'Task Manager'. Also, it will not close the new information window below the program interface window, have to close it manually.

hsavage

Second Report:

It appears, deleting, or, removing DebugMode.dat from the jv16 root folder and restarting beta3 eliminates the 'hanging in memory' problem previously reported. At least, in my case.

tullik

File Cleaner PT 2007 v 1.7.0.361

Temp dirs tab:

Checked: List all files from the computer's temp directories, but only files which have not been accessed in the last 5 days.

Repeatable problem: many (most) files listed were last accessed today.

Temp files tab:

Checked: Unneeded files, safe mode, but only files which have not been accessed in the last 5 days.

Repeatable problem: many (most) files listed were last accessed today.

Unused files tab:

Checked: List all files which have not been used in the last 999 days, modified in the last 999 days on drive C:\.

Options: use little cpu, skip deep, skip system.

Repeatable problems:
Tool lists 1000s of files.

Many (most?) files have been used or modified recently.

No way to stop or abort the tool.

Tool pegs the cpu, so closing tool is difficult.

Sometimes, after closing, though the task bar is clear, jv16pt.exe continues as a process using significant cpu

tullik

File Cleaner PT 2007 v 1.7.0.361

Temp dirs tab:

Checked: List all files from the computer's temp directories.

Found 215 files; selected all; clicked Remove button.

Result: 4 failed to access messages (not a problem, probable open files),

211 files removed with backup (no problem),

but results window lost focus and used all the cpu instead of putting out the ": All done!..." message.

Managed to close the tool's results window.

Listed names of files backed up.

Reran File Cleaner as above, 1 file removed with backup (the list of names), "All done" message appeared with no problem.

Then when attempting to scroll the message box below the main window, the font size suddenly became very large spontaneously:

Message box content after all the above happened:

: C:\DOCUME~1\Owner\LOCALS~1\Temp\, C:\WINDOWS\Temp\, C:\WUTemp\ analyzed.

: The File Cleaner is now finished. The found files are listed in the File Cleaner window.

Warning: Always verify the found files before removing them!

: Failed to access "C:\WINDOWS\Temp\Perflib_Perfdata_138.dat"!

: Failed to access "C:\WINDOWS\Temp\ZLT06ddb.TMP"!

: Failed to access "C:\WINDOWS\Temp\ZLT06db4.TMP"!

: Failed to access "C:\DOCUME~1\Owner\LOCALS~1\Temp\Perflib_Perfdata_fb8.dat"!

: C:\DOCUME~1\Owner\LOCALS~1\Temp\, C:\WINDOWS\Temp\, C:\WUTemp\ analyzed.

: The File Cleaner is now finished. The found files are listed in the File Cleaner window.

Warning: Always verify the found files before removing them!

: Failed to access "C:\DOCUME~1\Owner\LOCALS~1\Temp\Perflib_Perfdata_fb8.dat"!

: Failed to access "C:\WINDOWS\Temp\Perflib_Perfdata_138.dat"!

: Failed to access "C:\WINDOWS\Temp\ZLT06db4.TMP"!

: Failed to access "C:\WINDOWS\Temp\ZLT06ddb.TMP"!

: All done! 8.27 KB of data was removed (1 files and 0 directories).

guizop

about the duplicate file finder using up all the CPU:

the problem was only with this very directory. it took a long long time to finich it and after this all went normally. Maybe because it's filled with html files ? I'll give a second try with AV disabled just in case.

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.

drob

Regcleaner - abort still doesn't work properly, needs few clicks to get threads to one.

redseujac

Each time the "Messages Window" is open while and after running a Tool (e.g. 1Click Cleaner) and you "exit" the PowerTools Main Window (i.e. you're leaving the PT) , the "Messages Window" does not close. You have to do it manually.

Besides, jv16PT.exe "process" doesn't close either. You have to kill it manually in Windows Taskmanager.

Is that all on purpose or is it a bug? The latter, I guess :

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

Note: "evest" mentioned a similar behaviour here, but he talks about the "Debug Window", where obviously it concerns the "Messages Window". :

tullik

Registry Cleaner and ...

When Abort is clicked, that fact should be logged in the message box.

Also, please respond to this suggestion.

llynn4948

Seemed to work fine. Found and deleted 60 errors. then when I hit close, instead or returning to the icon window, it closed the regcleaner windown but left open the log window only.

Installation went easily.

jv16

tullik wrote

Also, please respond to this suggestion.

I'm not quite sure if I understood you correctly, are you saying the Abort buttons should be removed and their the Close buttons should work as the abort buttons?

tullik

jv16 wrote
tullik wrote

Also, please respond to this suggestion.

I'm not quite sure if I understood you correctly, are you saying the Abort buttons should be removed and their the Close buttons should work as the abort buttons?

Yes.

Although "Abort" is misleading. In Comp Sci, the term implies an error or malfunction. I just want/need to tell the tool(s) to stop populating the list, without throwing it away ..

~~Next Page »~~