Registry Compactor

gabrielmorrow

good news is it works on boot time compaction part

bad news is that now there is a bug with the phase 2 part the same bug

also you should consinder adding a service so you wont need to have uac prompts on jv16 powertools

leonardo

gabrielmorrow wrote
.....The good news is it works on boot time compaction part,

bad news is that now there is a bug with the phase 2 part the same bug.........

Confirmed:

Compactor phase-1 is now ok, compactor phase-2 contains the same errors as before.

jv16PT b1141_RegCompactor_Phase-2.jpg

arctucas

I tried the final version (2.1.0.1141) but encountered the same issue with phase 2, until I tried the suggestion of hsimpson409 and uninstalled Power Tools completely and then re-installed.

Now the Registry Compactor functions properly.

Thanks for resolving this.

gabrielmorrow

You can install the new version over any previous versions of jv16 PowerTools 2012. seems to be wrong registry compactor (stage 2) works after uninstalling and reinstalling

leonardo

Arctucas wrote
I tried the final version (2.1.0.1141) but encountered the same issue with phase 2, until I tried the suggestion of hsimpson409 and uninstalled Power Tools completely and then re-installed.

Now the Registry Compactor functions properly.......

Confirmed indeed!

After the uninstall of build1141 i did a fresh install of build 1141, after that a reboot. Now the compactor phase-1 and phase-2 is working OK.

NB: that reboot following the fresh installation of build1141 was really needed to make the compactor function correctly.

jv16

gabrielmorrow wrote
You can install the new version over any previous versions of jv16 PowerTools 2012. seems to be wrong registry compactor (stage 2) works after uninstalling and reinstalling

There should not be a need to uninstall. I have now rebuilt the 2.1.0.1141 installation package and uploaded it to our servers.

The rebuilt was done in a way it now forces the RegCompactor module to be always installed with the new one from the installation file. This should make sure that the problem gets solved from now on (i.e. with users who now download the latest version), without the need for an uninstall.

The version number is still the same, 2.1.0.1141, because the application itself is still the same, only the installer has been adjusted.

Can some new user please confirm that downloading and installing the latest build now and installing it over the previous version without uninstallation, does indeed fix the RegCompact problem?

nicomorr

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.

speedskater

jv16 wrote
Can some new user please confirm that downloading and installing the latest build now and installing it over the previous version without uninstallation, does indeed fix the RegCompact problem?

Worked for me as it should - no problems at all. (Windows 7 x64)

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.

gabrielmorrow

only issue remaining is phase two seems to think/want to compact HKEY_LOCAL_MACHINE\COMPONENTS but says its none existent

just found out that portion of registry does not exist unless you open the turn windows fetures on or off window in windows 7 by default

then even after making it says to large compression to be safe

nicomorr

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.

parkd1

This is what I get not when I run it.

reg.jpg

nicomorr

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

jv16 wrote
There should not be a need to uninstall. I have now rebuilt the 2.1.0.1141 installation package and uploaded it to our servers.

The rebuilt was done in a way it now forces the RegCompactor module to be always installed with the new one from the installation file. This should make sure that the problem gets solved from now on (i.e. with users who now download the latest version), without the need for an uninstall.

The version number is still the same, 2.1.0.1141, because the application itself is still the same, only the installer has been adjusted.

Can some new user please confirm that downloading and installing the latest build now and installing it over the previous version without uninstallation, does indeed fix the RegCompact problem?

Test 1. With W7-SP1 x86:

Previously Installed only jv16PT 2011 build 1053, never a 2012 (beta) version was installed on this system.

1. Uninstalled b1053, including backups and settings,

2. rebooted W7,

3. Installed jv16PT 2012 build 1141,

4. Ran 'CFMC' and 'Registry Cleaner' and 'fixed' the found errors,

5. Ran 'Registry compactor', both phase-1 and -2 executed without errors.

Test 2. With W7-SP1 x86 and XP-SP3:

Previously installed was jv16PT 2012 build 1132 and compaction has been done before with b1132.

1. Installed build 1141 over build 1132,

2. Ran 'CFMC' and 'Registry Cleaner' and 'fixed' the found errors,

3. Ran 'Registry compactor', phase-1 completed without errors but phase-2 completed with the well known errors

4. Ran the 'Registry compactor' for a second time, but with the same results as mentioned in point 3.

5. Booted 2x and deleted all Compactor files using the tool 'Program maintenance'

6. Ran 'Registry compactor' again, phase-1 completed without errors but phase-2 completed with the well known errors.

redseujac

Build 1141 without uninstalling previous version of this build.

Registry compactor ran as it should.

teunis

Build 1141 corrects the first phase, the second phase still shows the translation file problem - Win7-64HP.

Regards, Teunis

budgallxp

I also installed Build 1141 over prior version and confirm that it corrected the first phase, but the second phase still shows the translation file problem - Win7-64 64 bit

Bud Gallagher

mrcs

I don't know if this will help, but I would get the same DOSBox messages as the above screenshot in "jv16 PowerTools 2010" (never could use 2011) *unless* I remembered to rename another installed version, which was just plain "jv16 PowerTools". My best guess was that either the application not looking for the current installation or was not written to read the full name of the directory.

erockman

Just installed Build 1141 over existing 1141. I have W7 64 bit SP-1 Home Premium fully updated and patched on Dell laptop. Ran regcleaner and compactor. Compactor ran Phase 1 fine. However in phase 2, got the translation error.

jv16

This build should fix the issue also for Phase2:

http://www.macecraft.com/phpBB3/viewtopic.php?f=30&t=4701

« Previous Page Next Page »