Windows PE and Python 2.6 (Side-by-Side error)

[Werner Merkl]

Hallo,


I like Python 2.6 and I like to use it anywhere, even within Windows PE.

In former version of Python (<= 2.5.x) it was easy to bring it to a
Windows PE system: Install Python to Windows XP or Vista and (robo-)
copy the whole directory off Python (and all sub directories) to the
Windows PE system, adapt the path and it works.

With Python 2.6 I receive errors in the kind of '''Error: The
Side-by-Side configuration information in
"d:\4_debug\python26\PYTHON.EXE" contains errors. The application has
failed to start because its side-by-side configuration is incorrect.
Please see the application event log for more detail (14001).
Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module.'''

What I did: I copied all DLLs which DEPWALK found to C:\Python26, but
the error remained...

Has anyone an idea?


Thank you in advance
Werner

 

[Mark Tolonen]

Hallo,


I like Python 2.6 and I like to use it anywhere, even within Windows PE.

In former version of Python (<= 2.5.x) it was easy to bring it to a
Windows PE system: Install Python to Windows XP or Vista and (robo-)
copy the whole directory off Python (and all sub directories) to the
Windows PE system, adapt the path and it works.

With Python 2.6 I receive errors in the kind of '''Error: The
Side-by-Side configuration information in
"d:\4_debug\python26\PYTHON.EXE" contains errors. The application has
failed to start because its side-by-side configuration is incorrect.
Please see the application event log for more detail (14001).
Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module.'''

What I did: I copied all DLLs which DEPWALK found to C:\Python26, but the
error remained...

Has anyone an idea?


Thank you in advance
Werner

You'll need to install the Microsoft C runtime redistributables. An
installer to do this is buried in Microsoft Visual Studio 2008. The are
installed to the C:\Windows\WinSxS subdirectory. Take a look at this
directory and see if Microsoft really has solved "DLL Hell".

-Mark

 

[Martin v. Löwis]

Has anyone an idea?

You should not install "for all users" before copying it,
but "just for me".

Regards,
Martin

 

[Werner Merkl]

You should not install "for all users" before copying it,
but "just for me".

Regards,
Martin

This works! Thank you very much! (Sorry for the delay. I had been on a
conference, than I was ill and than, there were more urgent things...)

But now PyScripter may not use Python 2.6 internally. E. g., if I load a
python-dll (import bz2) I receise an Runtime ERROR! R6034...


Again, thanx a lot
Werner