jv16 PowerTools 2010 RC1 (latest build: 961)

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.

doogie

AL K. Hall wrote
Now I feel rather foolish; I reinstalled jv16 Power Tools and left the 'Add to Programs and Features' box checked

jv16setupCapture.PNG

(I have always unchecked all the boxes because I prefer not to install extra shortcuts, translations, etc.), and I now have an entry in the Windows Uninstall list as well as CCleaner.

I suppose I should really take the time to carefully examine all the options when installing.

Anyway, it appears that there is actually no problem, and I apologize for wasting everyone's time.

You haven't wasted anyones time so don't apologize.

Your questions were well founded and fitted in well with what myself and Leonardo are experiencing. In fact your posts were a big help to me as I looked deeper into the problem.

leonardo

DooGie wrote
AL K. Hall wroteNow I feel rather foolish; I reinstalled jv16 Power Tools and left the 'Add to Programs and Features' box checked

jv16setupCapture.PNG

(I have always unchecked all the boxes because I prefer not to install extra shortcuts, translations, etc.), and I now have an entry in the Windows Uninstall list as well as CCleaner.

I suppose I should really take the time to carefully examine all the options when installing.

Anyway, it appears that there is actually no problem, and I apologize for wasting everyone's time.

You haven't wasted anyones time so don't apologize.

Your questions were well founded and fitted in well with wat myself and Leonardo are experiencing. In fact your posts were a big help to me as I looked deeper into the problem.

Unfortunately one "uninstall" problem still exists in my XP-Pro-SP3 system with jv16 v2.0.0.961.

I have installed BOTH jv16PT-2009-build 606 AND jv16PT-2010-build 961.

They both show up in Windows Add/Remove software, in Revo Uninstaller, but ONLY 2009 build 606 shows in jv16-2010-build 961 SW-Uninstaller!

During Beta7 and RC1 one entry in jv16 Uninstaller showed jv16-2009-build 606 and one other showed jv16-2010-beta7-build xxx or jv16-2010-RC1-build xxx.

In the official release 2.0.0.961 something must have been changed.

doogie

Ironic isn't it that after the months of beta testing we are plagued by a bug in the uninstall routine :)

tbh though I think it will turn out to be a bug that is easily fixed.

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

AL K. Hall wrote

If you mean the Uninstall.exe located in Program Files(x86)>jv16 Power tools 2010>Uninstall, I meant that I get this when I try to execute it:

This stupid issue will be fixed in the next release. For some idiotic reason, the Uninstall.exe doesn't work without a correct command line parameter. The reasons behind this can only be answered by the people who develop the installation system PowerTools 2010 uses.

But starting with the next released version the \Uninstall folder will contain a working Uninstall shortcut that calls the Uninstall.exe with the correct parameters.

alk.hall

jv16 wrote
AL K. Hall wrote

If you mean the Uninstall.exe located in Program Files(x86)>jv16 Power tools 2010>Uninstall, I meant that I get this when I try to execute it:

This stupid issue will be fixed in the next release. For some idiotic reason, the Uninstall.exe doesn't work without a correct command line parameter. The reasons behind this can only be answered by the people who develop the installation system PowerTools 2010 uses.

But starting with the next released version the \Uninstall folder will contain a working Uninstall shortcut that calls the Uninstall.exe with the correct parameters.

Thank you.

When might we expect the Final, please?

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.

alk.hall

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.

« Previous Page