× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yeah, that's true, windows only complains if you try to use something within the directories it designates for program installation.

But I prefer the "run as administrator" fix. I like having all of my program files to be within the C:\Program Files* directories. And it's where tools (including the MS tool that's trying to protect me, causing this problem in the first place) expect programs to be.

The "Run As Administrator" is only needed during installation.


On 10/17/2012 8:43 AM, David Gibbs wrote:
On 10/16/2012 6:49 PM, Scott Klement wrote:
I've found that it helps to right-click and choose "Run As
Administrator" on my machine (which is Win7, 64 bit)

Without this, the installation was failing.
I've found that not installing in the default location eliminates the need to run as administrator.

The "Program Files" directories are protected by the OS and you have to run with escalated privileges in order to write anything to them.

If you install in a directory outside of "Program Files" you don't need to be administrator.

I usually use "C:\IBMRational".

david




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.