> On Wed, May 25, 2011 at 10:58 AM, Prof Brian Ripley
> wrote:
>> The following article has the most info I have found:
>>
>> http://msdn.microsoft.com/en-us/library/aa905330.aspx
>>
>> It includes:
>>
>> Before a 32 bit process is created, the following attributes are
>> checked to determine whet
On Wed, May 25, 2011 at 10:58 AM, Prof Brian Ripley
wrote:
> The following article has the most info I have found:
>
> http://msdn.microsoft.com/en-us/library/aa905330.aspx
>
> It includes:
>
> Before a 32 bit process is created, the following attributes are
> checked to determine whether it is an
On Wed, May 25, 2011 at 3:24 AM, JonY 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
The following article has the most info I have found:
http://msdn.microsoft.com/en-us/library/aa905330.aspx
It includes:
Before a 32 bit process is created, the following attributes are
checked to determine whether it is an installer:
Filename includes keywords such as "install," "setup,"
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, w
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 "acc
