jv16 PowerTools 2013 Release Candidate 1

siliconman01

Windows 8 x64 Professional on MS Surface Pro. Unit Testing Tool with 12 errors

vasek

Random Crashes 3rd + 4th

Closed the program and it crashed.

siliconman01

Windows 8 x64 Professional. CFMC crash.

1. Started the CFMC registry scan.

2. Aborted the scan ~15 seconds into the scan.

3. Program Aborted.

vasek

siliconman01 wrote
Windows 8 x64 Professional. CFMC crash.

1. Started the CFMC registry scan.

2. Aborted the scan ~15 seconds into the scan.

3. Program Aborted.

Is the crash reproducible?

Not cofirmed with Vista SP2 x86

leonardo

siliconman01 wrote
Windows 8 x64 Professional. CFMC crash.

1. Started the CFMC registry scan.

2. Aborted the scan ~15 seconds into the scan.

3. Program Aborted.

Not confirmed for W7-x64-SP1 with jv16PT-2013 RC1

leonardo

W7-x64-SP1 with jv16PT-2013_RC1:

This issue is still valid for RC1. Please see: http://www.macecraft.com/forum/viewtopic.php?f=10&t=4817#p31591

For my W7-x64 laptop: The 'Software Uninstaller' scan list, as produced by jv16PT-2012-b1173, is a better

representation of my installed software than the scan list produced by jv16PT-2013_RC1.

vasek

Leonardo wrote
The 'Software Uninstaller' scan list, as produced by jv16PT-2012-b1173, is a better

representation of my installed software than the scan list produced by jv16PT-2013_RC1.

I agree.

As I report here, the Secunia software is not listed in PT2013, but it is listed in PT2012. See the pictures below.

vasek

Boot Time Registry Compactor

Cannot translate texts of Boot Time Registry Compactor v 1.4 . Texts are still in English.

leonardo

W7-x64-SP1 with RC1:

Unit Testing Tool run generated 8 errors.

brama

Using Registry Cleaner with default options, when the scan is done, I chose to fix errors and floppy disk driver A: start to work, even without a diskette in.

It is ON during all the fixin process.

I think this is not correct.

Tested with W7 pro x64 sp1.

leonardo

Brama wrote
Using Registry Cleaner with default options, when the scan is done, I chose to fix errors and floppy disk driver A: start to work, even without a diskette in it. It is ON during all the fixing process.

I think this is not correct. Tested with W7 pro x64 sp1.

Your are right, this 'floppy disk drive' issue exists for 'some time' and jv16 made several attempts to fix it.

EDITED:

The floppy drive is only 'searched' during the fixing of the 'Invalid file or directory reference' items

leonardo

W7-x64-SP1 with RC1.

Disk wiper, Free Space only:

This issue still exists in RC1. See http://www.macecraft.com/phpBB3/viewtopic.php?f=10&t=4811&start=15#p31474

-After clicking 'Abort' the Disk wipe task continues in the background (as shown by the Task Manager) until the free space wiping is finished.

-Closing the 'jv16PT Main window' finishes the running Task manager process (jv16PT.exe).

-The green progress bar is not following the Disk wipe process correctly. Wiping process completed successful when the progress bar showed ~60% completion.

vasek

Confirmed. See jv16PT_debuglog_RC1_DiskWiper.html and Disk Wiper.jpg.

Leonardo wrote
W7-x64-SP1 with RC1.

Disk wiper, Free Space only:

.

This issue still exists in RC1. See http://www.macecraft.com/phpBB3/viewtopic.php?f=10&t=4811&start=15#p31474
.
-After clicking 'Abort' the Disk wipe task continues in the background (as shown by the Task Manager) until the free space wiping is finished.

-Closing the 'jv16PT Main window' finishes the running Task manager process (jv16PT.exe).

-The green progress bar is not following the Disk wipe process correctly. Wiping process completed successful when the progress bar showed ~60% completion.

hevesij.

I don't understand what is the reason for the difference.

Untitled-1.jpg

leonardo

Hevesi J. wrote
I don't understand what is the reason for the difference.

Untitled-1.jpg

After the initial installation of RC1 you should first run CFMC (Clean and Fix my Computer)

By design the 'PC health' and 'Registry health' indicators are set after a CFMC scan (preferred with the Normal cleaning policy) followed by fixing/deleting of the found items!

- If you fix ALL found errors, the health indicators will be set to 100%

- If you fix a PART of the found errors the health indicators will be set to <100% depending on the ratio of the found/fixed errors

tullik

Version 3.0.0.1248 (RC1) on 32-bit Windows 7

Backups:

jv16 wrote
tullik wroteAs reported here --> http://www.macecraft.com/phpBB3/viewtopic.php?p=31595#p31595 many previous PowerTools versions create an incorrect backup of REG_MULTI_SZ values. The issue also exists in Beta6.

Nice one! This is now fixed, thank you for reporting. The fix will be included to the next released version.

jv16 wrote
Bug fix: The program can create an incorrect backup for special registry data types

The backup for the test case of member liamZ now correctly restores the deleted value.

However, some issues remain:

#1 - The backup Entries.reg created by the Registry Finder line context menu is empty, i.e, it contains only header information.

Windows Registry Editor Version 5.00

; File created by TBackupManager
; Component version: 1.4.2
; Component used by: jv16 PowerTools 2013
; Program version: 3.0.0.1248
; File Description: MS bug (Context menu backup)
; Date: 21.03.2013
; Time: 21

#2 - Although the backup created by a Registry Finder delete action correctly restores the deleted value when done from the Backup tool's primary window, a restore done from the Custom restore window only restores part of the value. #2a - Only part of the value displays in the Custom restore window; namely, hex(7),00,32,00,33,00,34,00,35,00,36,00,37,00,38,00,39,00,30,00,\."

Windows Registry Editor Version 5.00

; File created by TBackupManager
; Component version: 1.4.2
; Component used by: jv16 PowerTools 2013
; Program version: 3.0.0.1248
; File Description: Registry Finder - Selected: 1, total: 7 (MS bug - backup via delete)
; Date: 21.03.2013
; Time: 21



"MSBug2"=hex(7),00,32,00,33,00,34,00,35,00,36,00,37,00,38,00,39,00,30,00,\

  39,00,38,00,37,00,36,00,35,00,34,00,33,00,32,00,31,00,00,00,00,00

#3 - The partial custom restore done at #2 may somehow be otherwise incorrect. Why? A subsequent Registry Finder search for "1234567890" fails to find the restored item (MSBug2CRW). It finds the other three items shown below.

Capture MS Bug items.JPG

Notes:
- MSBug2CRW (custom restore window) data terminates with four binary zeroes.
  
  MSBug2manual data entered manually terminates with eight binary zeroes.

leonardo

W7-x64-SP1 with RC1:

'Main menu' -> 'Backups' -> 'Registry Backups' and 'File Backups'.

1. CFMC creates 'File Backups', these contain both Registry items and File items.

2. Registry Cleaner creates 'Registry Backups', these only contain Registry items.

Deleting a registry backup generates a warning message that the backup contains both Registry and File items. This is rather confusing and I think it is not correct.

IMHO this particular warning message should only be issued at the deletion of 'File Backups'.

BackupDeleteWarning.jpg

parkd1

Has anyone used the registry compactor yet? I ran it and it missed up my computer. As far as I could see there were no error messages. Restore fixed it. So before you try it out do a restore point first.

leonardo

parkd1 wrote
Has anyone used the registry compactor yet? I ran it and it missed up my computer. As far as I could see there were no error messages. Restore fixed it. So before you try it out do a restore point first.

I ran Registry compactor yesterday on W7-x64-SP1. From the compactor log the result looked OK!

However it seems that the compactor phase-2 (following the W7 restart) has disappeared.

parkd1

Leonardo wrote
parkd1 wroteHas anyone used the registry compactor yet? I ran it and it missed up my computer. As far as I could see there were no error messages. Restore fixed it. So before you try it out do a restore point first.

I ran Registry compactor yesterday on W7-x64-SP1. From the compactor log the result looked OK!

However it seems that the compactor phase-2 (following the W7 restart) has disappeared.

When Windows started the things did not load up but did when I did another boot up. Thing I did see was it like turned off aero glass running W7-x86-SP1. Maybe for added safety have it make a restore point before the registry compactor runs.

« Previous Page Next Page »