On Wed, May 25, 2011 at 3:24 AM, JonY <jo...@users.sourceforge.net> wrote: > On 5/24/2011 23:54, Ozkan Sezer wrote: >> Hi all: >> >> What makes the User Access Control thing of vista or w7 to trigger? >> If I compile my program for x64 using mingw-w64, the program runs >> just fine. If I compile it for x86 either by mingw or mingw-w64 and >> run it on vista or w7 x64 version, windows intercepts it claiming that >> it wants to "access my computer and may do evil things", and when I >> choose 'allow' than it opens up a new console instead of using the >> existing cmd.exe console. I don't have an x86 version of vista or >> w7 installed on my boxes so I don't know the behavior there. >> FWIW, code is here: http://uhexen2.sf.net/tmp/h2patch3-1.0.0.9.tar.gz >> which is an application of xdelta3 (http://xdelta.org/) in progress >> and nothing oh so fanciful. >> >> Thanks. > > IIRC its based on executable file names and some other criteria which > I'm not sure of. > > See the Cygwin patch.exe.manifest file, there might be clues there. > >
Thanks. Found several references and finally found myself at Jim's site here: http://jesusnjim.com/programming/common-compiler-switches.html#manifest So, adding a manifest to the exe solved it. <rant>The whole thing is stupid btw: They are relying on an app's name having a substring of "patch" or "install",. Bah.. And I was running the app in my home directory and not from a system-wide place. Double-bah... </rant> -- Ozkan ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
