467,920 Members | 1,261 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,920 developers. It's quick & easy.

ImportError: MemoryLoadLibrary failed loading

Hi,

Recently I began my journey into creating executables. I am using
Andrea
Gavana's cool GUI2EXE program which works very well and that is a GUI
for
py2ece. I am also using Inno Setup to create a script/executable.
Anyway,
today I am putting the program to the test with some volunteer testers
and
I've hit a wall. On the first tester's PC the program installed
beautifully and runs great. The next tester's PC, the program failed
to
run complaining that MSVCR71.dll didn't exist. I copied that file on
there and now I get the following traceback written to my exe's log
file:

Traceback (most recent call last):
File "reminder.py", line 23, in ?
File "zipextimporter.pyo", line 78, in load_module
File "wx\__init__.pyo", line 45, in ?
File "zipextimporter.pyo", line 78, in load_module
File "wx\_core.pyo", line 4, in ?
File "zipextimporter.pyo", line 91, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd

I see other user's have this issue too sometimes and they talk a lot
about
a "gdiplus.dll" file. My user's PC has that file in 4 places on her
computer and my development PC has it in 6 places. Does either DLL
have to
be in a specific location for the executable to find it? Is this
something
else entirely? I tried sticking the gdiplus.dll file in the directory
my
executable runs from too, but that didn't work either.

I have posted this to the wxPython's group and the py2exe group, but
the latter doesn't have much activity and the wxPython suggestions
didn't work.

Thanks a lot!
Mike

Jul 9 '07 #1
  • viewed: 5940
Share:
1 Reply
On Jul 9, 12:47 pm, kyoso...@gmail.com wrote:
Hi,

Recently I began my journey into creating executables. I am using
Andrea
Gavana's cool GUI2EXE program which works very well and that is a GUI
for
py2ece. I am also using Inno Setup to create a script/executable.
Anyway,
today I am putting the program to the test with some volunteer testers
and
I've hit a wall. On the first tester's PC the program installed
beautifully and runs great. The next tester's PC, the program failed
to
run complaining that MSVCR71.dll didn't exist. I copied that file on
there and now I get the following traceback written to my exe's log
file:

Traceback (most recent call last):
File "reminder.py", line 23, in ?
File "zipextimporter.pyo", line 78, in load_module
File "wx\__init__.pyo", line 45, in ?
File "zipextimporter.pyo", line 78, in load_module
File "wx\_core.pyo", line 4, in ?
File "zipextimporter.pyo", line 91, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd

I see other user's have this issue too sometimes and they talk a lot
about
a "gdiplus.dll" file. My user's PC has that file in 4 places on her
computer and my development PC has it in 6 places. Does either DLL
have to
be in a specific location for the executable to find it? Is this
something
else entirely? I tried sticking the gdiplus.dll file in the directory
my
executable runs from too, but that didn't work either.

I have posted this to the wxPython's group and the py2exe group, but
the latter doesn't have much activity and the wxPython suggestions
didn't work.

Thanks a lot!

Mike
I figured this out, not that anyone probably cares. It seems the
program was looking for MSVCP71.dll, but I (alas) included the
MSVCR71.dll instead. If I include the correct file, it works. For all
the newbs out there, spelling makes a difference!

Mike

Jul 11 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Cousin Stanley | last post: by
reply views Thread by Ben McBride | last post: by
reply views Thread by Ajay | last post: by
1 post views Thread by kencana | last post: by
1 post views Thread by Sjoerd | last post: by
2 posts views Thread by Simon Forman | last post: by
reply views Thread by Andrew MacIntyre | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.