× 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.




On 2012-10-18, at 9:57 AM, wdsci-l-request@xxxxxxxxxxxx wrote:

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.

For me that was not the case Scott. Until I ignored the default and used my own directory (as David suggested) I could not apply updates. It would blow up during the process - something to do with being unable to overwrite files.

Maybe if the install had been run originally under "Run As Administrator" then maybe that problem doesn't occur. I am the administrator on my machine so (foolishly apparently) I assumed that "Run As Administrator" was not needed.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.