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



Compatibility was the key!

I just tried it with and without compatibility. With it on, it pushed the UAC prompt. With it off, no prompt!

Thanks, that has been annoying as all get out.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC


On 3/29/2011 9:48 AM, David Gibbs wrote:
Jim Oberholtzer wrote:
> 0.6 as well. Yes compatibility mode (XP sp3) is turned on.
If you've set the program to be compatible with XP, then it automatically has admin rights... which is causing the UAC dialog.

> For grins, I created a directory called c:\Utility. Copied all the
> files from c:\Putty into it. Created a shortcut and put it on the
> desktop.
> > No UAC prompt..... Now I do see a change in the icon. The old
> version still has the shield on it, the new one does not. I have no
> idea what the difference is other than I don't get the prompt. I'm
> good with that.
The shield indicates that Windows thinks it's a setup program. It's got some naming rules that can trigger this. If the word "setup", "update", or "install" is in the file name ... it automatically forces the UAC dialog when it's run. I ran into this on a PC app I developed (for Implementer) that did nothing to modify the Windows configuration. The programs name, however was "implementer-update.exe".

If the programs name was "putty.exe", I can't imagine why that would cause the UAC dialog ... except the XP compatibility.

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.