Jump to content

  • Log In with Google      Sign In   
  • Create Account


[RESOLVED] _except_handler4_common, vista, xp, help!!


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
3 replies to this topic

#1 makdaddy_98102   Members   -  Reputation: 122

Like
0Likes
Like

Posted 15 May 2008 - 06:22 PM

[THIS PROBLEM WAS DUE TO NOT USING THE STANDARD DIRECTX INSTALLER IN THE SDK'S REDIST FOLDER, AND INSTEAD TRYING TO DISTRIBUTE INDIVIDUAL .DLLS MANUALLY. THANKS FOR THE HELP.] I am building a game using DirectX. I'm running Windows Vista and using Visual C++ 2008 Express Edition. I downloaded the Aug 2007 DirectX SDK and I'm using the Direct9 APIs. I'm basing my code on the "Textures" sample project included withe the sdk (which is a devstudio 7.1 project that got automatically upgraded to devstudio 9 by vc 2008 express). The game makes some meshes, does some texturing, applies some matrix transformations. Nothing fancy. The game builds and runs fine on Vista. When I send the .exe file, along with the files d3d9.dll and d3dx9_35.dll to my friend who's running xp, as soon as he starts it he gets an error: "The procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll" I sent my friend the source code (the devstudio 9 .sln, the .vcproj, and the c++ and .h files) and he downloaded the same Aug 2007 sdk and built that same project on xp (although with Visual Studio Professional 2008, not Express 2008 like me), and it works without giving that error when it runs on xp. So what's going on? I did some reading and ran Dependency Walker on my .exe. I understand that msvcrt.dll is an operating-system-specific file, and it's fine if the vista version has a function that the xp version doesn't. Dependency Walker does indeed show that _except_handler4_common is referenced by some module that is referenced by my executable, but as far as I can tell it's only referenced indirectly by other system dlls (i.e., vista-specific dlls), not by my code directly and not by d3dx9_35.dll directly. So I can't understand who's referencing it, and why it works when built on xp. Any help appreciated. Michael [Edited by - makdaddy_98102 on May 16, 2008 9:59:36 PM]

Sponsor:

#2 makdaddy_98102   Members   -  Reputation: 122

Like
0Likes
Like

Posted 15 May 2008 - 06:58 PM

Thanks for the reply. I guess that's possible, but: He already had Visual Studio 2008 Pro installed on his xp machine when my game deployment originally didn't work for him, so wouldn't he have had (the equivalent of) the latest runtime stuff installed just by virtue of that? Or is it possible that installing the Aug 2007 SDK somehow installed the needed runtime stuff? I wish I understood this stuff.


#3 mtrudder   Members   -  Reputation: 129

Like
0Likes
Like

Posted 15 May 2008 - 07:10 PM

You're right, I jumped past the part where he had VS2008 installed. My bad. :P

After searching a bit in Google, it looks like this is a known issue in VC++ which has been floating around since Vista came out. I'd be interested to see if someone has come across a solution.

#4 makdaddy_98102   Members   -  Reputation: 122

Like
0Likes
Like

Posted 16 May 2008 - 03:09 AM

Thanks again. Can you post a link where it describes this being a general problem in VC++? Note: I didn't have this problem with a 2D (gdi+) version of the game built with the same Vista/VC2008Express system. So that's why I posted it here, because it seems to be tied to DirectX in some way.





Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS