Re: [Py2exe-users] Issue with py2exe: Access Denied error

[anil <an...@xs...>]

Hey Mark,

Thanks for thkinking along. You have a point re: the policy.

No, it's the same XP machine it's compiled on and then fails to run on. 
I asked someone else to compile it (even though he has a Win7 machine). 
Runs on his, but not on my xp or any other xp box. Same with the program 
I compiled on my XP box: does not run on my XP box or any other XP box, 
but does so on Win7.

Where should I be looking for extra dlls? I see a libray.zip in the 
dist folder and a python2.7.dll but nothing else.

I even tried this with python 2.5 and 2.6, but no luck.

rgds,
Anil

On 2012-08-02 01:45, Mark Hammond wrote:
> On 1/08/2012 8:18 PM, anil wrote:
>> Hi Mark,
>>
>> No it was built on XP, but does not run on XP. However the same XP 
>> build
>> does run on Win7.
>> I'm going to try the exec() the IE from a C program and see if it
>> results in the same.
>>
>> If so, we can rule out py2exe and it probably is a policy setting
>
> Well - if it runs from python.exe but does not run from py2exe on the
> exact same machine, then it wouldn't seem a policy setting to me.
>
> If it is a *different* XP machine that it fails to run on, I'd still
> be looking for extra DLLs that are being copied.  But apart from 
> that,
> I'm out of ideas :(
>
> Cheers,
>
> Mark
>
>>
>> Rgds,
>> Anil
>>
>> On 2012-08-01 10:58, Mark Hammond wrote:
>>> On 1/08/2012 6:00 PM, anil wrote:
>>>> I did find out that if I try this executable on a Win7 PC, it does 
>>>> work
>>>> (even without the change to the cwd). So seems to be related to XP 
>>>> (or
>>>> the setup that I have), in combination with py2exe.
>>>
>>> Was it also built on Win7?  If so, check the built directory for
>>> extra DLLs that you don't recognize or aren't certain you need -
>>> py2exe will sometimes pick up ones from the OS and when they load 
>>> on
>>> xp "random" things go wrong...
>>>
>>> Cheers,
>>>
>>> Mark
>>