🔒 Locked

Problem with running a DirectX9 program.

Started by shaqdx May 8, 2006 at 6:41 AM 7 replies 1k views

Original Post

May 8, 2006 at 6:41 AM

Hi, I have passed on a demo I wrote using the DirectX 9.0 October 2005 SDK to 2 of my friends and passed along the DLL installer required to run the demos. But for some strange reason, the demos don't work. My demos need the "d3dx9_27.dll" file, and my friends also have this installed on their machine. When they run the demo, an error comes up asking for this exact file, even though they already have it. They both have the latest DX version, and they have put the DLL file in the Windows/System32 folder aswell as the folder of my demo exe, but still nothing. Does anyone know what the problem might be? Thanks

Muhammad Haggag

May 8, 2006 at 9:36 AM

Well, try to make them open your application with dependency walker. If there's a problem with the DLL or finding it, dependency walker will tell you what the problem is.

Also, try to make them use the latest DirectX web installer.

shaqdx

May 8, 2006 at 5:59 PM

OK, I'll give it a go.

Flimflam

May 8, 2006 at 8:55 PM

Just a quick stupid mistake check, are you sure it's not asking for "d3dx9d_27.dll"? =)

I suspect this might be the case. A few people in the past have made the same mistake.

shaqdx

May 9, 2006 at 5:23 AM

I'm pretty sure my friends said it was "d3dx9_27.dll", but I'll check to make sure. On the other hand, my demo was complied on release mode, so I would assume it wouldn't ask for the debug version.

Evil Steve

May 9, 2006 at 7:37 AM

Quote:
Original post by shaqdx
I'm pretty sure my friends said it was "d3dx9_27.dll", but I'll check to make sure. On the other hand, my demo was complied on release mode, so I would assume it wouldn't ask for the debug version.

Actually, it depends on the .lib file you link to. You can still build a release app with debug libraries - it's just not a good idea [smile]

weasalmongler

May 9, 2006 at 7:41 AM

Make sure that they have the latest DirectX Runtime, April 2006 I think is the latest.

I had this problem with a few people on my team, they installed the latest runtime and all the problems went away.

EDIT: Sorry, just noticed that you said they do have it on their machine. Its still probably worth giving it a go though.

shaqdx

May 22, 2006 at 6:04 AM

I think Flimflam was right. My friends didn't look at the file name properly and it was the "d3dx9d_27.dll" that was being asked.

Am I right in thinking that to change this for a release app, I need to go to Project Properties->Linker->Input->Additional Dependencies->.. and add "d3dx9.lib". I currently have "d3dx9d.lib", so I am assuming that's where I went wrong.

jollyjeffers

May 22, 2006 at 6:22 AM

Quote:
Original post by shaqdx
Am I right in thinking that to change this for a release app, I need to go to Project Properties->Linker->Input->Additional Dependencies->.. and add "d3dx9.lib". I currently have "d3dx9d.lib", so I am assuming that's where I went wrong.

That should do the trick. Depending on whatever else you're using in your project, make sure you're not linking to other debug libraries...

Jack

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.