jv16 PowerTools 2010 Beta7 released! (Latest build: 948)

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.

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

redseujac wrote
siliconman01 wrote... The backup files of registry compactor are not removed via the Tools>Program Maintenance>Remove Registry Compactor backups.

Confirmed.

And that's regrettable.

This issue should be fixed asap.

It will be fixed, hopefully with the next build.

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.

siliconman01

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.

leonardo

siliconman01 wrote
Windows 7 x86 Professional and Windows 7 x64 Professional, PT B946

For those who want to clean up their system following a registry compact, I offer the following technique that I use.

This is for Windows 7 (x86 and x64) and Vista (x86 and x64). It will probably be applicable to XP systems; however, I have no XP system to test it on.

2. Do a search of the C:\ drive using the search term jv16pt_bak

3. Delete all files that include the term jv16pt_bak. These files will have extensions of .bak or .bak2 or .log or .log1 or .log2

4. Do a search of the C:\ drive using the search term *.blf

6. Do a search of the C:\drive using the search term regtrans-ms

XP-Pro-SP3 only finds hits for 'jv16pt_bak', 0 hits for '*.blf' and 'regtrans-ms'

siliconman01

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

Unit Testing Tool

Unfortunately halted (after 1878 seconds, 851502 tests performed and 12 errors) during FileTools test RawWriteFile.

Message: Cannot create file "C:\PT_UnitTestFile.dat", The process has no access to the file because the file is in use by another process".

the 12 errors found are:

97 s. - Error: TestRDA: FNE rate of 43,60 is larger than accepted! : 872 SubID = 2000 Par1 = 0 Par2 = 0


114 s. - Error: TestRDA: FNE rate of 46,20 is larger than accepted! : 924 SubID = 2000 Par1 = 0 Par2 = 0
665 s. - Error: TestRDA: FNE rate of 46,60 is larger than accepted! : 932 SubID = 2000 Par1 = 0 Par2 = 0
668 s. - Error: TestRDA FPO item: "%h:\Favorites\Microsoft Windows\Reatogo-X-PE =  BartPE +XPE -  BartPE - autoHelp - Plugins Repository 500+.url 7654432423 .exe / 123.exe" : 1 SubID = 1 Par1 = 0 Par2 = 0
681 s. - Error: TestRDA: FPO rate of 0,05 is larger than accepted! : 1 SubID = 2000 Par1 = 0 Par2 = 0
698 s. - Error: TestRDA: FNE rate of 46,30 is larger than accepted! : 926 SubID = 2000 Par1 = 0 Par2 = 0
1177 s. - Error: TestRDA: FNE rate of 44,55 is larger than accepted! : 891 SubID = 2000 Par1 = 0 Par2 = 0
1195 s. - Error: TestRDA: FNE rate of 43,40 is larger than accepted! : 868 SubID = 2000 Par1 = 0 Par2 = 0
1638 s. - Error: TestRDA: FNE rate of 45,40 is larger than accepted! : 908 SubID = 2000 Par1 = 0 Par2 = 0
1672 s. - Error: TestRDA: FNE rate of 43,85 is larger than accepted! : 877 SubID = 2000 Par1 = 0 Par2 = 0

1873 s. - Error: TestFileTools : 5 SubID = 0 Par1 = 01234 Par2 = -18700130044546288771617204471-1204304943-1117339572

leonardo

Running XP-Pro-SP3 with jv16PT-2101-build 946:

I ran the Unit Test tool 3 times,

-- twice it ran to completions with 13 errors of the kind: Error: TestRDA: FNE rate of 55,xx is larger than accepted.....

-- only once it crashed with the known message: "Cannot create file "C:\PT_UnitTestFile.dat". The process has no access to the file because file is in use by another process".

doogie

Tried out the Unit Test Tool on Windows 7 x64 with no problems.

siliconman01

Windows 7 x86 Professional and Windows 7 x64 Professional.

For users who run PerfectDisk 11 Professional on their Win 7 systems, I ran a test on both Win 7 x86 and Win 7 x64 to see what happens if PerfectDisk's boot time defrag is set to occur on a reboot at the same time jv16's registry compact is executed. This test shows that:

1. On reboot, PerfectDisk boot time defrag runs and defrags files/metadata that are normally defragged at boot time. Once the defrag is completed, PerfectDisk issues a fresh system restart to begin.

2. The fresh restart begins as it should.

3. Then jv16 registry compactor executes and performs phase 1 of the registry compact.

4. The reboot then continues, Windows loads and phase 2 of the registry compact occurs.

5. The system is now fully booted up once phase 2 of registry compact completes.

Conclusion: There appears to be no conflict between PerfectDisk's boot time defrag and jv16's method of boot time registry defrag.

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.

siliconman01

Just an observation. There does not appear to be any Vista x86 or Vista x64 users testing PT 2010. Or at least none that are reporting problems here on the forum. For the sake of a successful launch of PT 2010, I hope that inhouse testing on Vista x86 and Vista x64 is intensive. There are enough significant differences between Vista and Windows 7 that a launch without intensive Vista testing will probably be a major hiccup. JMO. :(

siliconman01

Can you provide unique icons for the various shortcuts that are create via Tools>Add Shortcuts to Desktop for... ? Right now each of the components uses the jv16PT.exe icon. By this I mean when the shortcut is created on the desktop, it has the same icon as what is represented on the main window of jv16 for that specific component. Or provide these icons so that they can be manually attached for each of the shortcuts.

leonardo

Running XP-Pro-SP3 with jv16PT-2010-build946:

For test purposes I ran Registry Finder with keyword 'zone', knowing a huge number of hits would be found.

The Scan Report just mentioned 126.173 hits but than Registry Finder frooze.

I added a Screen shot and the Bugreport /Debuglog from a clean start!

siliconman01

Windows 7 x86 and x64 Professional.

After creating shortcuts via Tools>Add Shortcuts to Desktop, there is no way to end jv16Pt.exe after the specific tool runs. Using Close or the red X does not end jv16Pt.exe and it just sits in memory.

1. Create a desktop shortcut for registry cleaner.

2. Start registry cleaner via the desktop shortcut.

3. Complete the registry cleaning.

4. Click on Close

jv16pt.exe does not exit memory.

leonardo

siliconman01 wrote
Windows 7 x86 and x64 Professional.

After creating shortcuts via Tools>Add Shortcuts to Desktop, there is no way to end jv16Pt.exe after the specific tool runs.

Using Close or the red X does not end jv16Pt.exe and it just sits in memory.

1. Create a desktop shortcut for registry cleaner.

2. Start registry cleaner via the desktop shortcut.

3. Complete the registry cleaning.

4. Click on Close

jv16pt.exe does not exit memory.

Confirmed for XP-Pro-SP3

doogie

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.

doogie

The main Registry Cleaner window doesn't maintain it's size after a restart of PT.

If I resize the window after a scan upon restart the height is ok but the width has shrunk. Think this may be a widescreen monitor issue.

leonardo

DooGie wrote
The main Registry Cleaner window doesn't maintain it's size after a restart of PT.

If I resize the window after a scan upon restart the height is ok but the width has shrunk. Think this may be a widescreen monitor issue.

I have this 'problem' with XP-Pro-SP3 for a long time. It started with a beta following jv16pt 2009 b606.

ONLY the right border of the window returns to a default position (at ~80% of the width of my 15" laptop display) after the restart of jv16PT2010beta7-b940.

The left border line of the window and the top and bottom borderline of the window (=the width), do not change. See the attached screen shots.

But I can live with it.

« Previous Page Next Page »