jv16 PowerTools 2012 Release Candidate 1

leonardo

Vasek wrote
Disk Wiper crashes.

Steps to reproduction:

1. Run 'Disk Wiper',

2. Check the 'Wipe all data options' on the 'Settings' tab,

3. Click on the 'Start' button and then the 'Yes' button,

4. the crash.

Not confirmed for both XP-SP3 and W7-SP1 x86 with jv16PT-2012-RC1.

maximumdefiant

siliconman01 wrote
This applies to Windows 7 SP1 x64 and x86 Professional.

The Registry Compactor is getting a lot of "Internal Error STU-ID-1, Data=""" errors. Something is wrong with the English translation. In addition, if UAC is on, the compactor cannot/does not execute Phase 2 of the compact following the reboot.

This also applies to Windows XP SP3, x86 Pro.

The 1st use caused an error in Winlogon.exe, resulting in a BSOD. Further attempts didn't, and Windows loaded properly, but I still get the error messages in both phases.

redseujac

Vasek wrote
PowerTools crashes after close the History Cleaner. See jv16PT_debuglog_history.html and bugreport_history.txt.

Steps to reproduction:

1. Run History Cleaner,

2. click on the Close button,

3. close the aplication,

4. the crash (after a while).

Confirmed .

redseujac

Vasek wrote
The captions of the following tools cannot translate:

File tool and Directory tool.

Edit: Also caption in the Immunize my Computer.

Confirmed for the Dutch language.

redseujac

Vasek wrote
Cannot translate the Delete item in context menu in the Mass rename tool. See Mass Renamer.jpg

Confirmed for the Dutch language.

tullik

V.2.1.0.1119 on x86 Windows 7:

File Tool:

Test conditions:
* All test files are .dat files from a PT2011 Settings folder.

* These columns are specified to always appear: Size, the three dates, Attributes.

* The tests are conducted using the icons.

Change Attributes issues:
* When you change the attributes of one or more files, the changes do not show in the list. The changes show immediately in a windows explorer window concurrently open on the files.

* Sometimes the file attributes remove/add window comes up too small to use. It usually comes up correctly after closing the too small window and clicking the Change Attributes icon again.

Too small CA window.JPG

* When a file has all four attributes on, only the Archive attribute shows in the list.

* When a file has all four attributes off, the Archive attribute shows in the list as on.

tullik

V.2.1.0.1119 on x86 Windows 7:

File Tool:

Test conditions:
* All test files are .dat files from a PT2011 Settings folder.

* These columns are specified to always appear: Size, the three dates, Attributes.

* The tests are conducted using the icons.

Copy to issue:
* When you select some files and click the Copy to icon, the content of all the file lines disappears. It comes back when you complete the Copy to operation.

tullik

V.2.1.0.1119 on x86 Windows 7:

File Tool:

Test conditions:
* All test files are .dat files from a PT2011 Settings folder.

* These columns are specified to always appear: Size, the three dates, Attributes.

* The tests are conducted using the icons.

Explore issue:
* When you select a file (say the sixth one in the list), and an earlier one in the list is highlighted but not selected, clicking the Explore icon brings up the widows explorer window with the earlier file highlighted, not the selected one.

tullik

V.2.1.0.1119 on x86 Windows 7:

File Tool:

Test conditions:
* All test files are .dat files from a PT2011 Settings folder.

* These columns are specified to always appear: Size, the three dates, Attributes.

* The tests are conducted using the icons.

Merge issue:
* When you select two files and click the Merge icon, the text in ALL the file lines disappears when the "Please give the new filename" dialog appears. The text returns after completing the dialog.

[deleted]

Leonardo wrote
'File Tools' -> 'File Tool' does not have these left/right small scroll arrows to scroll through the top icons left/right. I guess this is a bug!

'File Tools' -> 'File Finder' and other tools in 'File Tools' do have these small left/right small scroll arrows.

Thanks for reporting, I have now made the File Tools toolbar scrollable. The reason this toolbar looks different is that the 'toolbar' in most other windows is actually a pagecontrol widget, so it has different functionality.

leonardo

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.

jv16

siliconman01 wrote
In setting up the Global Ignore List, I inadvertently specified my desired entries as G\, H\, I\, etc., instead of G:\, H:\, I:\, etc. (left off the colon.). This bad info was accepted by the Settings and added to the Global Ignore List. HOWEVER, this caused the several of the elements of jv16 to totally fail. Registry cleaner found nothing, CFMC found nothing, the Startup Manager did not find all RUN entries, the Unit Test Tool collapsed and aborted, and Syscache.dat was only 8 kbytes in size instead of 243 kbytes.

This is why some of my previous posts in this thread has been voided. Once I found this input bug, posted failures no longer occurred.

jv16 needs to check the validity of a global ignore entry. Or better yet, properly parse various entry styles such as:

AGHIJKLMNO or A,G,H, or A\, G\, H\

This is by design. The Global Ignore List works just like any Ignore List features of the software, that is, you can enter any generic search words or phrases you want the product to ignore. Therefore, it's technically accepted that user enters for example "A" to the Global Ignore List, and this causes the product to skip any and all data containing the letter "a", that is, quite a lot of data.

jv16

Leonardo wrote
rdtmk5 wroteFile Tool - if the tool window is not maximized, there's no way to scroll to the right-most buttons on the button bar. Depending on the size of the window, the tool bar ends in the middle of an icon and I can't move past that point to select other buttons to the right without re-sizing the window.

'File Tools' -> 'File Tool' does not have these left/right small scroll arrows to scroll through the top icons left/right. I guess this is a bug!

'File Tools' -> 'File Finder' and other tools in 'File Tools' do have these small left/right small scroll arrows.

.

I'm afraid this is by design. The Toolbar component used in the File Tools and Directory Tool do not support such a scrolling feature. The "tool bar" in for example File Finder is not actually a toolbar at all, but a tabbed component and that's why it does support scrolling.

siliconman01

jv16 wrote
siliconman01 wroteIn setting up the Global Ignore List, I inadvertently specified my desired entries as G\, H\, I\, etc., instead of G:\, H:\, I:\, etc. (left off the colon.). This bad info was accepted by the Settings and added to the Global Ignore List. HOWEVER, this caused the several of the elements of jv16 to totally fail. Registry cleaner found nothing, CFMC found nothing, the Startup Manager did not find all RUN entries, the Unit Test Tool collapsed and aborted, and Syscache.dat was only 8 kbytes in size instead of 243 kbytes.

This is why some of my previous posts in this thread has been voided. Once I found this input bug, posted failures no longer occurred.

jv16 needs to check the validity of a global ignore entry. Or better yet, properly parse various entry styles such as:

AGHIJKLMNO or A,G,H, or A\, G\, H\

This is by design. The Global Ignore List works just like any Ignore List features of the software, that is, you can enter any generic search words or phrases you want the product to ignore. Therefore, it's technically accepted that user enters for example "A" to the Global Ignore List, and this causes the product to skip any and all data containing the letter "a", that is, quite a lot of data.

I urge you to re-examine the "design". The Global Ignore List was initially implemented several versions back to provide jv16 the ability to ignore disks/drives/partitions that the user did not want jv16 to examine any data that was on those specific disks/drives/partitions. Therefore user entry into the Global Ignore List should only be recognized as disk/drives/partitions designations. Personally I see no rational in leaving such a glaring cavity that permits a user to screw up jv16's performance via a user input error.

tullik

siliconman01 wrote
jv16 wrote
siliconman01 wroteIn setting up the Global Ignore List, I inadvertently specified my desired entries as G\, H\, I\, etc., instead of G:\, H:\, I:\, etc. (left off the colon.). This bad info was accepted by the Settings and added to the Global Ignore List. HOWEVER, this caused the several of the elements of jv16 to totally fail. Registry cleaner found nothing, CFMC found nothing, the Startup Manager did not find all RUN entries, the Unit Test Tool collapsed and aborted, and Syscache.dat was only 8 kbytes in size instead of 243 kbytes.

This is why some of my previous posts in this thread has been voided. Once I found this input bug, posted failures no longer occurred.

jv16 needs to check the validity of a global ignore entry. Or better yet, properly parse various entry styles such as:

AGHIJKLMNO or A,G,H, or A\, G\, H\

This is by design. The Global Ignore List works just like any Ignore List features of the software, that is, you can enter any generic search words or phrases you want the product to ignore. Therefore, it's technically accepted that user enters for example "A" to the Global Ignore List, and this causes the product to skip any and all data containing the letter "a", that is, quite a lot of data.

I urge you to re-examine the "design". The Global Ignore List was initially implemented several versions back to provide jv16 the ability to ignore disks/drives/partitions that the user did not want jv16 to examine any data that was on those specific disks/drives/partitions. Therefore user entry into the Global Ignore List should only be recognized as disk/drives/partitions designations. Personally I see no rational in leaving such a glaring cavity that permits a user to screw up jv16's performance via a user input error.

At times, it can be useful to ignore strings other than the lettercolonbackwardslash format of partition drive letters.

"Global" in this context means "comprehensive, total".

Perhaps when the user is updating the Global Ignore List, a warning to use extra care would be appropriate.

jv16

siliconman01 wrote

I urge you to re-examine the "design". The Global Ignore List was initially implemented several versions back to provide jv16 the ability to ignore disks/drives/partitions that the user did not want jv16 to examine any data that was on those specific disks/drives/partitions. Therefore user entry into the Global Ignore List should only be recognized as disk/drives/partitions designations. Personally I see no rational in leaving such a glaring cavity that permits a user to screw up jv16's performance via a user input error.

At this point of development, the only way I can "fix" this is to add the following confirmation:

71 = You are about to ignore a lot of items, are you sure you know what you are doing?

In case the user attempts to add a string to the Global Ignore List that seems very short, e.g. "C\" or "C"

jv16

Vasek wrote
An useless dialog after closes the Immunize my computer tool. See Immunize my computer.jpg

Steps to reproduction:

1. Go to Settings and uncheck the "Allow Immunize my computer feature to check..." option on the Network features tab,

2. perhaps restart the aplication,

3. click on the Immunize my computer,

4. click on the No button,

5. click on the Close button.

This is now fixed, thank you for reporting!

jv16

Vasek wrote
A missing Action history item in the File menu. See Action History.jpg

Or this is by design?

This is now fixed, thank you for reporting!

jv16

Vasek wrote
PowerTools crashes after close the History Cleaner. See jv16PT_debuglog_history.html and bugreport_history.txt.

Steps to reproduction:

1. Run History Cleaner,

2. click on the Close button,

3. close the aplication,

4. the crash (after a while).

This is now fixed, thank you for reporting!

« Previous Page Next Page »