0
0

Thought I would put this out to the general forum. I am having some troubles with EventSystem_Create. Whenever I try to call it to create a eventSystem I’m getting two “Unable to open VxD, Error Code: 2” errors, on after another? I then get three exception errors. The weird thing is, after clicking through the 2 error message boxes and ‘continuing’ through the exceptions, it works! I have run the the same code on two seperate machines, both using Audigy 2 ZS’s but one is XP SP2 and the other is 2k. Same result on both. I am able to get the demo to run without the error messages or exceptions, which is a little strange. I’m able to use the System_Create call without any problem. Any ideas or suggestions?

  • You must to post comments
0
0

I’m not blue screening, just an error message indicating a VxD (doesn’t say which one) and the standard pop-up exception. There are a lot of differences between our application and the test app. I was hoping that someone might have seen this. It almost seems like a conflict with another library or driver. The really weird thing is that it works, but only after I get through the error messages. Need to find out where the error message is coming from..

blue

  • You must to post comments
0
0

Yeah, that was my next step.. As I said, I was hoping somebody had already come across this and save me some time.. If not, I get to do some good old fashion debugging.. 😆

blue

  • You must to post comments
0
0

I suggest testing it out in an emulator like Virtual PC or QEMU or something to see if it might be an issue related to your Audigy cards. (Of course, if you’re using an Audigy hardware feature, that’s probably not feasible…) Creative hardware and drivers give me nonstop headaches, and I vaguely remember having VxD errors back when I had an Audigy.

  • You must to post comments
0
0

That is what I’m trying to figure out now. What VxD is causing the problem? I have our app’s guts all torn out and I’m stepping through the code. We use some proprietary hardware and drivers that may be causing a problem. As soon as I get the FMOD source code, I am interested to see if the problem is really even with FMOD or not. I’m think that it’s not, however obviously releated. If you guys come across something, let me know. When I find the solution I’ll post it here.

  • You must to post comments
0
0

[quote="Blue Solitare":3llzrqhq]That is what I’m trying to figure out now. What VxD is causing the problem? I have our app’s guts all torn out and I’m stepping through the code. We use some proprietary hardware and drivers that may be causing a problem. As soon as I get the FMOD source code, I am interested to see if the problem is really even with FMOD or not. I’m think that it’s not, however obviously releated. If you guys come across something, let me know. When I find the solution I’ll post it here.[/quote:3llzrqhq]You might want to try profiling your application in Dependency Walker to see what DLLs and VxDs it tries to load – usually the profile function will catch missing files.

  • You must to post comments
0
0

Never used Dependency Walker before, cool app! That’s what it took to find that problem. An old .dll that we don’t use (why it was still in our bin folder, I’m not sure) was conflicting with ctagent.dll (creative library). Deleted the old .dll, problem solved. No errors! Thanks guys for your help.

  • You must to post comments
Showing 6 results
Your Answer

Please first to submit.