Thread: [PyOpenGL-Users] Python 2.7 and msvcr71.dll
Brought to you by:
mcfletch
From: Eli S. (Gmail) <wic...@gm...> - 2011-02-08 20:01:05
|
Hello, When I import OpenGL.GL like this under windows XP: Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import OpenGL.GL I get the following error in an alert box: python.exe - Unable To Locate Component This application has failed to start becuase MSVCR71.dll was not found. Re-installing the application may fix this problem. The same behavior occurs when trying to import OpenGL.GL from inside our application, however, aside from the alert box, the application seems to run fine (we're able to use OpenGL just fine, see 3d stuff, shaders, etc. etc.). PyOpenGL was installed via easy_install: >>> OpenGL.GL.__file__ 'C:\\Python27\\lib\\site-packages\\pyopengl-3.0.1-py2.7-win32.egg\\OpenGL\\GL\\__init__.pyc' Any suggestions on what we need to do to get this (seemingly spurious) alert to go away? Thanks, Eli |
From: Stephen H. <sho...@us...> - 2011-02-08 20:56:22
|
i think the dll comes from visual studio 2005 or 2008. The newer versions of python do not come with these files I think. It gave me trouble trying to install python on windows 7 so I am stuck using python on my laptop with windows xp since my laptop has visual studio. On Tue, Feb 8, 2011 at 12:00 PM, Eli Stevens (Gmail) <wic...@gm...>wrote: > Hello, > > When I import OpenGL.GL like this under windows XP: > > Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit > (Intel)] on win32 > Type "help", "copyright", "credits" or "license" for more information. > >>> import OpenGL.GL > > I get the following error in an alert box: > > python.exe - Unable To Locate Component > This application has failed to start becuase MSVCR71.dll was not > found. Re-installing the application may fix this problem. > > The same behavior occurs when trying to import OpenGL.GL from inside our > application, however, aside from the alert box, the application seems to run > fine (we're able to use OpenGL just fine, see 3d stuff, shaders, etc. etc.). > > PyOpenGL was installed via easy_install: > > >>> OpenGL.GL.__file__ > > 'C:\\Python27\\lib\\site-packages\\pyopengl-3.0.1-py2.7-win32.egg\\OpenGL\\GL\\__init__.pyc' > > Any suggestions on what we need to do to get this (seemingly spurious) > alert to go away? > > Thanks, > Eli > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-users > > |
From: Eli S. (Gmail) <wic...@gm...> - 2011-02-08 21:26:53
|
According to http://www.py2exe.org/index.cgi/Tutorial#Step51 , msvcr71.dll is from VS 2005, while python 2.6 and newer use VS 2008 (and hence msvcr90.dll). Since I'm on python 2.7, it should be using msvcr90.dll, not 71. :-/ I guess I should have included that in my original email. I guess I'm trying to ask "why does PyOpenGL ask for a .dll that's clearly out of date with respect to the python version that I'm using?" You can install the MSVS 2008 Express Edition for free; that's what I've done and it works fine (for example, we also use a lot of Cython, and it uses VS 2008). Eli On Tue, Feb 8, 2011 at 12:55 PM, Stephen Hopkins <sho...@us...> wrote: > i think the dll comes from visual studio 2005 or 2008. The newer versions > of python do not come with these files I think. It gave me trouble trying to > install python on windows 7 so I am stuck using python on my laptop with > windows xp since my laptop has visual studio. > > On Tue, Feb 8, 2011 at 12:00 PM, Eli Stevens (Gmail) <wic...@gm... > > wrote: > >> Hello, >> >> When I import OpenGL.GL like this under windows XP: >> >> Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit >> (Intel)] on win32 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> import OpenGL.GL >> >> I get the following error in an alert box: >> >> python.exe - Unable To Locate Component >> This application has failed to start becuase MSVCR71.dll was not >> found. Re-installing the application may fix this problem. >> >> The same behavior occurs when trying to import OpenGL.GL from inside our >> application, however, aside from the alert box, the application seems to run >> fine (we're able to use OpenGL just fine, see 3d stuff, shaders, etc. etc.). >> >> PyOpenGL was installed via easy_install: >> >> >>> OpenGL.GL.__file__ >> >> 'C:\\Python27\\lib\\site-packages\\pyopengl-3.0.1-py2.7-win32.egg\\OpenGL\\GL\\__init__.pyc' >> >> Any suggestions on what we need to do to get this (seemingly spurious) >> alert to go away? >> >> Thanks, >> Eli >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> PyOpenGL Homepage >> http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list >> PyO...@li... >> https://lists.sourceforge.net/lists/listinfo/pyopengl-users >> >> > |
From: Alejandro S. <as...@gm...> - 2011-02-08 22:56:36
|
Hello Eli, On Feb 8, 2011, at 7:26 PM, "Eli Stevens (Gmail)" <wic...@gm...> wrote: > According to http://www.py2exe.org/index.cgi/Tutorial#Step51 , msvcr71.dll is from VS 2005, while python 2.6 and newer use VS 2008 (and hence msvcr90.dll). Since I'm on python 2.7, it should be using msvcr90.dll, not 71. :-/ I guess I should have included that in my original email. I guess I'm trying to ask "why does PyOpenGL ask for a .dll that's clearly out of date with respect to the python version that I'm using?" It might have to do with the compiler version used for compiling python.exe. If it was built using VS 2005, it's expectable that it depends on msvcrt71. I guess the question here would be where did you download the Python interpreter you are using from? Did you get it from the official website? > You can install the MSVS 2008 Express Edition for free; that's what I've done and it works fine (for example, we also use a lot of Cython, and it uses VS 2008). You can also get these dll files by downloading and installing the Microsoft Visual C++ redistributable package. It's a free download and will spare you (and your users) from having to install Visual Studio. Please notice there are different redistibutable versions, each one corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. Hope this helps. Alejandro.- > On Tue, Feb 8, 2011 at 12:55 PM, Stephen Hopkins <sho...@us...> wrote: > i think the dll comes from visual studio 2005 or 2008. The newer versions of python do not come with these files I think. It gave me trouble trying to install python on windows 7 so I am stuck using python on my laptop with windows xp since my laptop has visual studio. > > On Tue, Feb 8, 2011 at 12:00 PM, Eli Stevens (Gmail) <wic...@gm...> wrote: > Hello, > > When I import OpenGL.GL like this under windows XP: > > Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)] on win32 > Type "help", "copyright", "credits" or "license" for more information. > >>> import OpenGL.GL > > I get the following error in an alert box: > > python.exe - Unable To Locate Component > This application has failed to start becuase MSVCR71.dll was not found. Re-installing the application may fix this problem. > > The same behavior occurs when trying to import OpenGL.GL from inside our application, however, aside from the alert box, the application seems to run fine (we're able to use OpenGL just fine, see 3d stuff, shaders, etc. etc.). > > PyOpenGL was installed via easy_install: > > >>> OpenGL.GL.__file__ > 'C:\\Python27\\lib\\site-packages\\pyopengl-3.0.1-py2.7-win32.egg\\OpenGL\\GL\\__init__.pyc' > > Any suggestions on what we need to do to get this (seemingly spurious) alert to go away? > > Thanks, > Eli > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-users > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-users |
From: Silverstein <her...@sc...> - 2011-02-09 01:27:31
|
> > You can also get these dll files by downloading and installing the > Microsoft Visual C++ redistributable package. It's a free download and > will spare you (and your users) from having to install Visual Studio. > > Please notice there are different redistibutable versions, each one > corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. There are also different releases for each of these typically. For example, the initial release or a service pack (like an SP1) release. For example: Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en |
From: Jonathan H. <ta...@ta...> - 2011-02-09 08:43:38
|
Beware: When downloading the redistributable installer for MSVCR90.dll, it is important not to use the SP1 version of the installer. This contains the wrong version of MSVCR90.dll. A similar problem *may* exist with the redistributable installer for MSVCR71.dll, linked to below. It may contain a wrong version of MSVCR71.dll, which would cause problems. Someone with experience of this feel free to contradict me here. The original version of Microsoft Visual C++ 2005 Redistributable Package (x86), as linked to from the py2exe tutorial page: http://www.microsoft.com/downloads/en/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee ...is known to contain the correct version of MSVCR71.dll for Python 2.5. All of the above assumes you are using the compiled version of Python downloaded from python.org. If you compiled your own (or got it from someone else who compiled their own) then I don't know enough about your situation for any of my advice to be meaningful. Best regards, Jonathan On 08/02/2011 23:41, Silverstein wrote: > > >> >> You can also get these dll files by downloading and installing the >> Microsoft Visual C++ redistributable package. It's a free download >> and will spare you (and your users) from having to install Visual >> Studio. >> >> Please notice there are different redistibutable versions, each one >> corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. > There are also different releases for each of these typically. For > example, the initial release or a service pack (like an SP1) release. > For example: > > > Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) > > http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > > > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-users -- Jonathan Hartley Made of meat. http://tartley.com ta...@ta... +44 7737 062 225 twitter/skype: tartley |
From: Eli S. (Gmail) <wic...@gm...> - 2011-02-08 23:47:56
|
I'm using the standard windows binary installer for python 2.7, which (to the best of my knowledge) was compiled with VS 2008, and uses the msvcr90.dll, which I have (I know that I have them due to having to wrangle py2exe packing for the application). Again, my application works just fine, since python 2.7 uses msvcr90.dll. I don't actually need the msvcr71.dll that the alert box is talking about. I'm trying to figure out why importing OpenGL.GL is telling me that I need that file, when I actually don't need it (presenting end users with a spurious error message on startup isn't acceptable, especially for the support guys ;). Thanks for all the feedback, Eli On Tue, Feb 8, 2011 at 2:56 PM, Alejandro Segovia <as...@gm...> wrote: > Hello Eli, > > On Feb 8, 2011, at 7:26 PM, "Eli Stevens (Gmail)" <wic...@gm...> > wrote: > > According to <http://www.py2exe.org/index.cgi/Tutorial#Step51> > http://www.py2exe.org/index.cgi/Tutorial#Step51 , msvcr71.dll is from VS > 2005, while python 2.6 and newer use VS 2008 (and hence msvcr90.dll). Since > I'm on python 2.7, it should be using msvcr90.dll, not 71. :-/ I guess I > should have included that in my original email. I guess I'm trying to ask > "why does PyOpenGL ask for a .dll that's clearly out of date with respect to > the python version that I'm using?" > > > It might have to do with the compiler version used for compiling > python.exe. If it was built using VS 2005, it's expectable that it depends > on msvcrt71. > > I guess the question here would be where did you download the Python > interpreter you are using from? Did you get it from the official website? > > You can install the MSVS 2008 Express Edition for free; that's what I've > done and it works fine (for example, we also use a lot of Cython, and it > uses VS 2008). > > > You can also get these dll files by downloading and installing the > Microsoft Visual C++ redistributable package. It's a free download and will > spare you (and your users) from having to install Visual Studio. > > Please notice there are different redistibutable versions, each one > corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. > > Hope this helps. > > Alejandro.- > > On Tue, Feb 8, 2011 at 12:55 PM, Stephen Hopkins < <sho...@us...> > sho...@us...> wrote: > >> i think the dll comes from visual studio 2005 or 2008. The newer versions >> of python do not come with these files I think. It gave me trouble trying to >> install python on windows 7 so I am stuck using python on my laptop with >> windows xp since my laptop has visual studio. >> >> On Tue, Feb 8, 2011 at 12:00 PM, Eli Stevens (Gmail) <<wic...@gm...> >> wic...@gm...> wrote: >> >>> Hello, >>> >>> When I import OpenGL.GL like this under windows XP: >>> >>> Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit >>> (Intel)] on win32 >>> Type "help", "copyright", "credits" or "license" for more information. >>> >>> import OpenGL.GL >>> >>> I get the following error in an alert box: >>> >>> python.exe - Unable To Locate Component >>> This application has failed to start becuase MSVCR71.dll was not >>> found. Re-installing the application may fix this problem. >>> >>> The same behavior occurs when trying to import OpenGL.GL from inside our >>> application, however, aside from the alert box, the application seems to run >>> fine (we're able to use OpenGL just fine, see 3d stuff, shaders, etc. etc.). >>> >>> PyOpenGL was installed via easy_install: >>> >>> >>> OpenGL.GL.__file__ >>> >>> 'C:\\Python27\\lib\\site-packages\\pyopengl-3.0.1-py2.7-win32.egg\\OpenGL\\GL\\__init__.pyc' >>> >>> Any suggestions on what we need to do to get this (seemingly spurious) >>> alert to go away? >>> >>> Thanks, >>> Eli >>> >>> >>> ------------------------------------------------------------------------------ >>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>> Pinpoint memory and threading errors before they happen. >>> Find and fix more than 250 security defects in the development cycle. >>> Locate bottlenecks in serial and parallel code that limit performance. >>> <http://p.sf.net/sfu/intel-dev2devfeb> >>> http://p.sf.net/sfu/intel-dev2devfeb >>> _______________________________________________ >>> PyOpenGL Homepage >>> <http://pyopengl.sourceforge.net>http://pyopengl.sourceforge.net >>> _______________________________________________ >>> PyOpenGL-Users mailing list >>> <PyO...@li...> >>> PyO...@li... >>> <https://lists.sourceforge.net/lists/listinfo/pyopengl-users> >>> https://lists.sourceforge.net/lists/listinfo/pyopengl-users >>> >>> >> > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-users > > |
From: Alejandro S. <as...@gm...> - 2011-02-09 02:17:07
|
Hi Eli, On Feb 8, 2011, at 9:47 PM, "Eli Stevens (Gmail)" <wic...@gm...> wrote: > I'm using the standard windows binary installer for python 2.7, which (to the best of my knowledge) was compiled with VS 2008, and uses the msvcr90.dll, which I have (I know that I have them due to having to wrangle py2exe packing for the application). > > Again, my application works just fine, since python 2.7 uses msvcr90.dll. I don't actually need the msvcr71.dll that the alert box is talking about. I'm trying to figure out why importing OpenGL.GL is telling me that I need that file, when I actually don't need it (presenting end users with a spurious error message on startup isn't acceptable, especially for the support guys ;). Have you tried using "Dependency Walker" (depends.exe) to trace whether it's either Python or a dynamically loaded library (and which) is actually asking for msvcrt71? Alejandro.- > On Tue, Feb 8, 2011 at 2:56 PM, Alejandro Segovia <as...@gm...> wrote: > Hello Eli, > > On Feb 8, 2011, at 7:26 PM, "Eli Stevens (Gmail)" <wic...@gm...> wrote: > >> According to http://www.py2exe.org/index.cgi/Tutorial#Step51 , msvcr71.dll is from VS 2005, while python 2.6 and newer use VS 2008 (and hence msvcr90.dll). Since I'm on python 2.7, it should be using msvcr90.dll, not 71. :-/ I guess I should have included that in my original email. I guess I'm trying to ask "why does PyOpenGL ask for a .dll that's clearly out of date with respect to the python version that I'm using?" > > It might have to do with the compiler version used for compiling python.exe. If it was built using VS 2005, it's expectable that it depends on msvcrt71. > > I guess the question here would be where did you download the Python interpreter you are using from? Did you get it from the official website? > >> You can install the MSVS 2008 Express Edition for free; that's what I've done and it works fine (for example, we also use a lot of Cython, and it uses VS 2008). > > You can also get these dll files by downloading and installing the Microsoft Visual C++ redistributable package. It's a free download and will spare you (and your users) from having to install Visual Studio. > > Please notice there are different redistibutable versions, each one corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. > > Hope this helps. > > Alejandro.- > >> On Tue, Feb 8, 2011 at 12:55 PM, Stephen Hopkins <sho...@us...> wrote: >> i think the dll comes from visual studio 2005 or 2008. The newer versions of python do not come with these files I think. It gave me trouble trying to install python on windows 7 so I am stuck using python on my laptop with windows xp since my laptop has visual studio. >> >> On Tue, Feb 8, 2011 at 12:00 PM, Eli Stevens (Gmail) <wic...@gm...> wrote: >> Hello, >> >> When I import OpenGL.GL like this under windows XP: >> >> Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)] on win32 >> Type "help", "copyright", "credits" or "license" for more information. >> >>> import OpenGL.GL >> >> I get the following error in an alert box: >> >> python.exe - Unable To Locate Component >> This application has failed to start becuase MSVCR71.dll was not found. Re-installing the application may fix this problem. >> >> The same behavior occurs when trying to import OpenGL.GL from inside our application, however, aside from the alert box, the application seems to run fine (we're able to use OpenGL just fine, see 3d stuff, shaders, etc. etc.). >> >> PyOpenGL was installed via easy_install: >> >> >>> OpenGL.GL.__file__ >> 'C:\\Python27\\lib\\site-packages\\pyopengl-3.0.1-py2.7-win32.egg\\OpenGL\\GL\\__init__.pyc' >> >> Any suggestions on what we need to do to get this (seemingly spurious) alert to go away? >> >> Thanks, >> Eli >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> PyOpenGL Homepage >> http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list >> PyO...@li... >> https://lists.sourceforge.net/lists/listinfo/pyopengl-users >> >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> PyOpenGL Homepage >> http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list >> PyO...@li... >> https://lists.sourceforge.net/lists/listinfo/pyopengl-users > |
From: Eli S. (Gmail) <wic...@gm...> - 2011-02-09 07:34:25
|
Hello, :) The error can be provoked by "import OpenGL.GL" from the interactive prompt in Python, so it seems unlikely to be anything but PyOpenGL. I used dependency walker, and see the following tree: python.exe - python27.dll - _ctypes.pyd - opengl32.dll - gle32.dll - msvcr71.dll Obviously there are a ton of other files loaded as well; if any of them could be pertinent, let me know and I will search for them. Do other people's installs under python 2.7 not try and load msvcr71.dll? Additionally, after the alert box, dependency walker spat out hundreds of error messages like: GetProcAddress(0x5ED00000 [OPENGL32.DLL], "_FunctionType@108") called from "_CTYPES.PYD" at address 0x1D1A39C7 and returned NULL. Error: The specified procedure could not be found (127). I'm not sure if that's related or not. Thanks for helping me chase this down. :) Eli On Tue, Feb 8, 2011 at 6:16 PM, Alejandro Segovia <as...@gm...> wrote: > Hi Eli, > > On Feb 8, 2011, at 9:47 PM, "Eli Stevens (Gmail)" <wic...@gm...> > wrote: > > I'm using the standard windows binary installer for python 2.7, which (to > the best of my knowledge) was compiled with VS 2008, and uses the > msvcr90.dll, which I have (I know that I have them due to having to wrangle > py2exe packing for the application). > > Again, my application works just fine, since python 2.7 uses msvcr90.dll. > I don't actually need the msvcr71.dll that the alert box is talking about. > I'm trying to figure out why importing OpenGL.GL is telling me that I need > that file, when I actually don't need it (presenting end users with a > spurious error message on startup isn't acceptable, especially for the > support guys ;). > > > Have you tried using "Dependency Walker" (depends.exe) to trace whether > it's either Python or a dynamically loaded library (and which) is actually > asking for msvcrt71? > > Alejandro.- > > On Tue, Feb 8, 2011 at 2:56 PM, Alejandro Segovia < <as...@gm...> > as...@gm...> wrote: > >> Hello Eli, >> >> On Feb 8, 2011, at 7:26 PM, "Eli Stevens (Gmail)" <<wic...@gm...> >> wic...@gm...> wrote: >> >> According to <http://www.py2exe.org/index.cgi/Tutorial#Step51><http://www.py2exe.org/index.cgi/Tutorial#Step51> >> http://www.py2exe.org/index.cgi/Tutorial#Step51 , msvcr71.dll is from VS >> 2005, while python 2.6 and newer use VS 2008 (and hence msvcr90.dll). Since >> I'm on python 2.7, it should be using msvcr90.dll, not 71. :-/ I guess I >> should have included that in my original email. I guess I'm trying to ask >> "why does PyOpenGL ask for a .dll that's clearly out of date with respect to >> the python version that I'm using?" >> >> >> It might have to do with the compiler version used for compiling >> python.exe. If it was built using VS 2005, it's expectable that it depends >> on msvcrt71. >> >> I guess the question here would be where did you download the Python >> interpreter you are using from? Did you get it from the official website? >> >> You can install the MSVS 2008 Express Edition for free; that's what I've >> done and it works fine (for example, we also use a lot of Cython, and it >> uses VS 2008). >> >> >> You can also get these dll files by downloading and installing the >> Microsoft Visual C++ redistributable package. It's a free download and will >> spare you (and your users) from having to install Visual Studio. >> >> Please notice there are different redistibutable versions, each one >> corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. >> >> Hope this helps. >> >> Alejandro.- >> >> On Tue, Feb 8, 2011 at 12:55 PM, Stephen Hopkins < <sho...@us...><sho...@us...> >> sho...@us...> wrote: >> >>> i think the dll comes from visual studio 2005 or 2008. The newer versions >>> of python do not come with these files I think. It gave me trouble trying to >>> install python on windows 7 so I am stuck using python on my laptop with >>> windows xp since my laptop has visual studio. >>> >>> On Tue, Feb 8, 2011 at 12:00 PM, Eli Stevens (Gmail) <<wic...@gm...><wic...@gm...> >>> wic...@gm...> wrote: >>> >>>> Hello, >>>> >>>> When I import OpenGL.GL like this under windows XP: >>>> >>>> Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit >>>> (Intel)] on win32 >>>> Type "help", "copyright", "credits" or "license" for more information. >>>> >>> import OpenGL.GL >>>> >>>> I get the following error in an alert box: >>>> >>>> python.exe - Unable To Locate Component >>>> This application has failed to start becuase MSVCR71.dll was not >>>> found. Re-installing the application may fix this problem. >>>> >>>> The same behavior occurs when trying to import OpenGL.GL from inside our >>>> application, however, aside from the alert box, the application seems to run >>>> fine (we're able to use OpenGL just fine, see 3d stuff, shaders, etc. etc.). >>>> >>>> PyOpenGL was installed via easy_install: >>>> >>>> >>> OpenGL.GL.__file__ >>>> >>>> 'C:\\Python27\\lib\\site-packages\\pyopengl-3.0.1-py2.7-win32.egg\\OpenGL\\GL\\__init__.pyc' >>>> >>>> Any suggestions on what we need to do to get this (seemingly spurious) >>>> alert to go away? >>>> >>>> Thanks, >>>> Eli >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio >>>> XE: >>>> Pinpoint memory and threading errors before they happen. >>>> Find and fix more than 250 security defects in the development cycle. >>>> Locate bottlenecks in serial and parallel code that limit performance. >>>> <http://p.sf.net/sfu/intel-dev2devfeb><http://p.sf.net/sfu/intel-dev2devfeb> >>>> http://p.sf.net/sfu/intel-dev2devfeb >>>> _______________________________________________ >>>> PyOpenGL Homepage >>>> <http://pyopengl.sourceforge.net> <http://pyopengl.sourceforge.net> >>>> http://pyopengl.sourceforge.net >>>> _______________________________________________ >>>> PyOpenGL-Users mailing list >>>> <PyO...@li...><PyO...@li...> >>>> PyO...@li... >>>> <https://lists.sourceforge.net/lists/listinfo/pyopengl-users><https://lists.sourceforge.net/lists/listinfo/pyopengl-users> >>>> https://lists.sourceforge.net/lists/listinfo/pyopengl-users >>>> >>>> >>> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> <http://p.sf.net/sfu/intel-dev2devfeb> >> http://p.sf.net/sfu/intel-dev2devfeb >> >> _______________________________________________ >> PyOpenGL Homepage >> <http://pyopengl.sourceforge.net>http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list >> <PyO...@li...> >> PyO...@li... >> <https://lists.sourceforge.net/lists/listinfo/pyopengl-users> >> https://lists.sourceforge.net/lists/listinfo/pyopengl-users >> >> > |
From: Jonathan H. <ta...@ta...> - 2011-02-09 09:07:38
|
Ah, so does that imply that it's not Python2.7 which is using msvcr71, it's gle32.dll, which presumably was compiled against that version of the C runtime. That implies everything I said in my last email, about not using SP1, is barking up the wrong tree and can safely be ignored. You should provide whatever version of msvcr71 was used when gle32 was compiled. I'm not smart enough to help you determine that. Also, I presume that at some point, Python2.7 may also require msvcr90, and that can be provided using the (non SP1) download previously linked to. Cheers, Jonathan Eli Stephens wrote: Hello, :) The error can be provoked by "import OpenGL.GL" from the interactive prompt in Python, so it seems unlikely to be anything but PyOpenGL. I used dependency walker, and see the following tree: python.exe - python27.dll - _ctypes.pyd - opengl32.dll - gle32.dll - msvcr71.dll Obviously there are a ton of other files loaded as well; if any of them could be pertinent, let me know and I will search for them. Do other people's installs under python 2.7 not try and load msvcr71.dll? Additionally, after the alert box, dependency walker spat out hundreds of error messages like: GetProcAddress(0x5ED00000 [OPENGL32.DLL], "_FunctionType@108") called from "_CTYPES.PYD" at address 0x1D1A39C7 and returned NULL. Error: The specified procedure could not be found (127). I'm not sure if that's related or not. Thanks for helping me chase this down. :) Eli On 09/02/2011 08:43, Jonathan Hartley wrote: > Beware: When downloading the redistributable installer for > MSVCR90.dll, it is important not to use the SP1 version of the > installer. This contains the wrong version of MSVCR90.dll. > > A similar problem *may* exist with the redistributable installer for > MSVCR71.dll, linked to below. It may contain a wrong version of > MSVCR71.dll, which would cause problems. Someone with experience of > this feel free to contradict me here. > > The original version of Microsoft Visual C++ 2005 Redistributable > Package (x86), as linked to from the py2exe tutorial page: > > http://www.microsoft.com/downloads/en/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee > > ...is known to contain the correct version of MSVCR71.dll for Python 2.5. > > All of the above assumes you are using the compiled version of Python > downloaded from python.org. If you compiled your own (or got it from > someone else who compiled their own) then I don't know enough about > your situation for any of my advice to be meaningful. > > Best regards, > > Jonathan > > On 08/02/2011 23:41, Silverstein wrote: >> >> >>> >>> You can also get these dll files by downloading and installing the >>> Microsoft Visual C++ redistributable package. It's a free download >>> and will spare you (and your users) from having to install Visual >>> Studio. >>> >>> Please notice there are different redistibutable versions, each one >>> corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. >> There are also different releases for each of these typically. For >> example, the initial release or a service pack (like an SP1) >> release. For example: >> >> >> Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) >> >> http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> >> >> _______________________________________________ >> PyOpenGL Homepage >> http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list >> PyO...@li... >> https://lists.sourceforge.net/lists/listinfo/pyopengl-users > > -- > Jonathan Hartley Made of meat.http://tartley.com > ta...@ta... +44 7737 062 225 twitter/skype: tartley > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > > > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-users -- Jonathan Hartley Made of meat. http://tartley.com ta...@ta... +44 7737 062 225 twitter/skype: tartley |
From: Alejandro S. <as...@gm...> - 2011-02-09 12:24:19
|
Hello Eli, On Feb 9, 2011, at 7:07 AM, Jonathan Hartley <ta...@ta...> wrote: > Ah, so does that imply that it's not Python2.7 which is using msvcr71, it's gle32.dll, which presumably was compiled against that version of the C runtime. Okay, the problem seems to be in our OpenGL implementation then. Have you installed the latest video drivers for your video card or are you using the stock windows version? If you're on NVIDIA or ATI, upgrading your video drivers might help. Alejandro.- > Eli Stephens wrote: > > Hello, :) > > The error can be provoked by "import OpenGL.GL" from the interactive prompt in Python, so it seems unlikely to be anything but PyOpenGL. I used dependency walker, and see the following tree: > > python.exe > - python27.dll > - _ctypes.pyd > - opengl32.dll > - gle32.dll > - msvcr71.dll > > Obviously there are a ton of other files loaded as well; if any of them could be pertinent, let me know and I will search for them. Do other people's installs under python 2.7 not try and load msvcr71.dll? > > Additionally, after the alert box, dependency walker spat out hundreds of error messages like: > > GetProcAddress(0x5ED00000 [OPENGL32.DLL], "_FunctionType@108") called from "_CTYPES.PYD" at address 0x1D1A39C7 and returned NULL. Error: The specified procedure could not be found (127). > > I'm not sure if that's related or not. > > Thanks for helping me chase this down. :) > > Eli > > On 09/02/2011 08:43, Jonathan Hartley wrote: >> >> Beware: When downloading the redistributable installer for MSVCR90.dll, it is important not to use the SP1 version of the installer. This contains the wrong version of MSVCR90.dll. >> >> A similar problem *may* exist with the redistributable installer for MSVCR71.dll, linked to below. It may contain a wrong version of MSVCR71.dll, which would cause problems. Someone with experience of this feel free to contradict me here. >> >> The original version of Microsoft Visual C++ 2005 Redistributable Package (x86), as linked to from the py2exe tutorial page: >> >> http://www.microsoft.com/downloads/en/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee >> >> ...is known to contain the correct version of MSVCR71.dll for Python 2.5. >> >> All of the above assumes you are using the compiled version of Python downloaded from python.org. If you compiled your own (or got it from someone else who compiled their own) then I don't know enough about your situation for any of my advice to be meaningful. >> >> Best regards, >> >> Jonathan >> >> On 08/02/2011 23:41, Silverstein wrote: >>> >>> >>> >>>> >>>> You can also get these dll files by downloading and installing the Microsoft Visual C++ redistributable package. It's a free download and will spare you (and your users) from having to install Visual Studio. >>>> >>>> Please notice there are different redistibutable versions, each one corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. >>> There are also different releases for each of these typically. For example, the initial release or a service pack (like an SP1) release. For example: >>> Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) >>> >>> http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en >>> >>> >>> ------------------------------------------------------------------------------ >>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >>> Pinpoint memory and threading errors before they happen. >>> Find and fix more than 250 security defects in the development cycle. >>> Locate bottlenecks in serial and parallel code that limit performance. >>> http://p.sf.net/sfu/intel-dev2devfeb >>> >>> _______________________________________________ >>> PyOpenGL Homepage >>> http://pyopengl.sourceforge.net >>> _______________________________________________ >>> PyOpenGL-Users mailing list >>> PyO...@li... >>> https://lists.sourceforge.net/lists/listinfo/pyopengl-users >> >> -- >> Jonathan Hartley Made of meat. http://tartley.com >> ta...@ta... +44 7737 062 225 twitter/skype: tartley >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> >> _______________________________________________ >> PyOpenGL Homepage >> http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list >> PyO...@li... >> https://lists.sourceforge.net/lists/listinfo/pyopengl-users > > -- > Jonathan Hartley Made of meat. http://tartley.com > ta...@ta... +44 7737 062 225 twitter/skype: tartley > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-users |
From: Eli S. (Gmail) <wic...@gm...> - 2011-02-09 17:55:01
|
I'm not certain if I've got the absolute latest drivers, but they are reasonably updated. I see the problem on my Macbook Pro under Parallels, rebooted into Windows via Boot Camp, and on a dedicated Windows 7 machine (via py2exe). All exhibit the same behavior (pop up an alert box, then work fine); though I suspect that's because I'm not using anything provided by the gle32.dll. My Boot Camp partition is a fairly recent install, and I purposefully keep it minimal for testing purposes (ie. no old versions of Python, etc.). That probably doesn't match most testing environments; I could see a dependency on an old version of msvcr slipping through. What will it take to fix this? Should I start looking into recompiling PyOpenGL from source? Or will a fixed 3.0.2 come out in the near future? Thanks, Eli On Wed, Feb 9, 2011 at 4:23 AM, Alejandro Segovia <as...@gm...> wrote: > Hello Eli, > > On Feb 9, 2011, at 7:07 AM, Jonathan Hartley <ta...@ta...> wrote: > > Ah, so does that imply that it's not Python2.7 which is using msvcr71, it's > gle32.dll, which presumably was compiled against that version of the C > runtime. > > > Okay, the problem seems to be in our OpenGL implementation then. Have you > installed the latest video drivers for your video card or are you using the > stock windows version? > > If you're on NVIDIA or ATI, upgrading your video drivers might help. > > Alejandro.- > > Eli Stephens wrote: > > Hello, :) > > The error can be provoked by "import OpenGL.GL" from the interactive prompt > in Python, so it seems unlikely to be anything but PyOpenGL. I used > dependency walker, and see the following tree: > > python.exe > - python27.dll > - _ctypes.pyd > - opengl32.dll > - gle32.dll > - msvcr71.dll > > Obviously there are a ton of other files loaded as well; if any of them > could be pertinent, let me know and I will search for them. Do other > people's installs under python 2.7 not try and load msvcr71.dll? > > Additionally, after the alert box, dependency walker spat out hundreds of > error messages like: > > GetProcAddress(0x5ED00000 [OPENGL32.DLL], "_FunctionType@108") called from > "_CTYPES.PYD" at address 0x1D1A39C7 and returned NULL. Error: The specified > procedure could not be found (127). > > I'm not sure if that's related or not. > > Thanks for helping me chase this down. :) > > Eli > > On 09/02/2011 08:43, Jonathan Hartley wrote: > > Beware: When downloading the redistributable installer for MSVCR90.dll, it > is important not to use the SP1 version of the installer. This contains the > wrong version of MSVCR90.dll. > > A similar problem *may* exist with the redistributable installer for > MSVCR71.dll, linked to below. It may contain a wrong version of MSVCR71.dll, > which would cause problems. Someone with experience of this feel free to > contradict me here. > > The original version of Microsoft Visual C++ 2005 Redistributable Package > (x86), as linked to from the py2exe tutorial page: > > <http://www.microsoft.com/downloads/en/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee> > http://www.microsoft.com/downloads/en/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee > > ...is known to contain the correct version of MSVCR71.dll for Python 2.5. > > All of the above assumes you are using the compiled version of Python > downloaded from python.org. If you compiled your own (or got it from > someone else who compiled their own) then I don't know enough about your > situation for any of my advice to be meaningful. > > Best regards, > > Jonathan > > On 08/02/2011 23:41, Silverstein wrote: > > > > > You can also get these dll files by downloading and installing the > Microsoft Visual C++ redistributable package. It's a free download and will > spare you (and your users) from having to install Visual Studio. > > Please notice there are different redistibutable versions, each one > corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. > > There are also different releases for each of these typically. For > example, the initial release or a service pack (like an SP1) release. For > example: > Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) > <http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en> > http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. <http://p.sf.net/sfu/intel-dev2devfeb>http://p.sf.net/sfu/intel-dev2devfeb > > > _______________________________________________ > PyOpenGL Homepage <http://pyopengl.sourceforge.net>http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list <PyO...@li...>PyO...@li... <https://lists.sourceforge.net/lists/listinfo/pyopengl-users>https://lists.sourceforge.net/lists/listinfo/pyopengl-users > > > -- > Jonathan Hartley Made of meat. <http://tartley.com>http://tartley.com <ta...@ta...>ta...@ta... +44 7737 062 225 twitter/skype: tartley > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. <http://p.sf.net/sfu/intel-dev2devfeb>http://p.sf.net/sfu/intel-dev2devfeb > > > _______________________________________________ > PyOpenGL Homepage <http://pyopengl.sourceforge.net>http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list <PyO...@li...>PyO...@li... <https://lists.sourceforge.net/lists/listinfo/pyopengl-users>https://lists.sourceforge.net/lists/listinfo/pyopengl-users > > > -- > Jonathan Hartley Made of meat. <http://tartley.com>http://tartley.com <ta...@ta...>ta...@ta... +44 7737 062 225 twitter/skype: tartley > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-users > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > PyOpenGL Homepage > http://pyopengl.sourceforge.net > _______________________________________________ > PyOpenGL-Users mailing list > PyO...@li... > https://lists.sourceforge.net/lists/listinfo/pyopengl-users > > |
From: Alejandro S. <as...@gm...> - 2011-02-10 04:14:19
|
Hi Eli, On Wed, Feb 9, 2011 at 3:54 PM, Eli Stevens (Gmail) <wic...@gm...>wrote: > I'm not certain if I've got the absolute latest drivers, but they are > reasonably updated. I see the problem on my Macbook Pro under Parallels, > rebooted into Windows via Boot Camp, and on a dedicated Windows 7 machine > (via py2exe). All exhibit the same behavior (pop up an alert box, then work > fine); though I suspect that's because I'm not using anything provided by > the gle32.dll. > I've never used Parallels myself and I don't know how mature its OpenGL support might be, but personally, I would refrain from doing 3D development on a VM. > > My Boot Camp partition is a fairly recent install, and I purposefully keep > it minimal for testing purposes (ie. no old versions of Python, etc.). That > probably doesn't match most testing environments; I could see a dependency > on an old version of msvcr slipping through. > > What will it take to fix this? Should I start looking into recompiling > PyOpenGL from source? Or will a fixed 3.0.2 come out in the near future? > I am not sure. I would suggest you try to run py2exe on a native Windows (not inside a VM), creating the executable not inside a VM but on the real thing and with the latest video drivers. This may or may not help solve the problem, but it's something I would definitely try. Good luck! Alejandro.- > > On Wed, Feb 9, 2011 at 4:23 AM, Alejandro Segovia <as...@gm...>wrote: > >> Hello Eli, >> >> On Feb 9, 2011, at 7:07 AM, Jonathan Hartley <ta...@ta...> wrote: >> >> Ah, so does that imply that it's not Python2.7 which is using msvcr71, >> it's gle32.dll, which presumably was compiled against that version of the C >> runtime. >> >> >> Okay, the problem seems to be in our OpenGL implementation then. Have you >> installed the latest video drivers for your video card or are you using the >> stock windows version? >> >> If you're on NVIDIA or ATI, upgrading your video drivers might help. >> >> Alejandro.- >> >> Eli Stephens wrote: >> >> Hello, :) >> >> The error can be provoked by "import OpenGL.GL" from the interactive >> prompt in Python, so it seems unlikely to be anything but PyOpenGL. I used >> dependency walker, and see the following tree: >> >> python.exe >> - python27.dll >> - _ctypes.pyd >> - opengl32.dll >> - gle32.dll >> - msvcr71.dll >> >> Obviously there are a ton of other files loaded as well; if any of them >> could be pertinent, let me know and I will search for them. Do other >> people's installs under python 2.7 not try and load msvcr71.dll? >> >> Additionally, after the alert box, dependency walker spat out hundreds of >> error messages like: >> >> GetProcAddress(0x5ED00000 [OPENGL32.DLL], "_FunctionType@108") called >> from "_CTYPES.PYD" at address 0x1D1A39C7 and returned NULL. Error: The >> specified procedure could not be found (127). >> >> I'm not sure if that's related or not. >> >> Thanks for helping me chase this down. :) >> >> Eli >> >> On 09/02/2011 08:43, Jonathan Hartley wrote: >> >> Beware: When downloading the redistributable installer for MSVCR90.dll, it >> is important not to use the SP1 version of the installer. This contains the >> wrong version of MSVCR90.dll. >> >> A similar problem *may* exist with the redistributable installer for >> MSVCR71.dll, linked to below. It may contain a wrong version of MSVCR71.dll, >> which would cause problems. Someone with experience of this feel free to >> contradict me here. >> >> The original version of Microsoft Visual C++ 2005 Redistributable Package >> (x86), as linked to from the py2exe tutorial page: >> >> <http://www.microsoft.com/downloads/en/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee> >> http://www.microsoft.com/downloads/en/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee >> >> ...is known to contain the correct version of MSVCR71.dll for Python 2.5. >> >> All of the above assumes you are using the compiled version of Python >> downloaded from python.org. If you compiled your own (or got it from >> someone else who compiled their own) then I don't know enough about your >> situation for any of my advice to be meaningful. >> >> Best regards, >> >> Jonathan >> >> On 08/02/2011 23:41, Silverstein wrote: >> >> >> >> >> You can also get these dll files by downloading and installing the >> Microsoft Visual C++ redistributable package. It's a free download and will >> spare you (and your users) from having to install Visual Studio. >> >> Please notice there are different redistibutable versions, each one >> corresponding to msvcrt 71, 80 and 90 with both x86 and x64 flavors. >> >> There are also different releases for each of these typically. For >> example, the initial release or a service pack (like an SP1) release. For >> example: >> Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) >> <http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en> >> http://www.microsoft.com/downloads/en/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. <http://p.sf.net/sfu/intel-dev2devfeb>http://p.sf.net/sfu/intel-dev2devfeb >> >> >> _______________________________________________ >> PyOpenGL Homepage <http://pyopengl.sourceforge.net>http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list <PyO...@li...>PyO...@li... <https://lists.sourceforge.net/lists/listinfo/pyopengl-users>https://lists.sourceforge.net/lists/listinfo/pyopengl-users >> >> >> -- >> Jonathan Hartley Made of meat. <http://tartley.com>http://tartley.com <ta...@ta...>ta...@ta... +44 7737 062 225 <+447737062225> twitter/skype: tartley >> >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. <http://p.sf.net/sfu/intel-dev2devfeb>http://p.sf.net/sfu/intel-dev2devfeb >> >> >> _______________________________________________ >> PyOpenGL Homepage <http://pyopengl.sourceforge.net>http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list <PyO...@li...>PyO...@li... <https://lists.sourceforge.net/lists/listinfo/pyopengl-users>https://lists.sourceforge.net/lists/listinfo/pyopengl-users >> >> >> -- >> Jonathan Hartley Made of meat. <http://tartley.com>http://tartley.com <ta...@ta...>ta...@ta... +44 7737 062 225 <+447737062225> twitter/skype: tartley >> >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> >> _______________________________________________ >> PyOpenGL Homepage >> http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list >> PyO...@li... >> https://lists.sourceforge.net/lists/listinfo/pyopengl-users >> >> >> >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> PyOpenGL Homepage >> http://pyopengl.sourceforge.net >> _______________________________________________ >> PyOpenGL-Users mailing list >> PyO...@li... >> https://lists.sourceforge.net/lists/listinfo/pyopengl-users >> >> > -- Alejandro Segovia Azapian Director, Algorithmia: Visualization & Acceleration http://web.algorithmia.net |