Right, my guess would be you have a global constructor that is causing a .gpf and so LoadLibrary itself is failing.
There are ways to debug this (you can write a simple app which LoadLibrary's your client .dll and see what the error code/message is), including rolling back to a last known good state and examining all of your changes carefully. Yahn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 29, 2006 4:22 PM To: [email protected] Subject: Re: [hlcoders] Client dll not being used This is the same bug in the srcds core, unfortunately. In fact Valve probably copied the Quake 2 code directly because Quake 2 had this exact same annoying bug of failing to report dll load issues and continuing. That was the first thing I fixed when they open sourced it. :) Try http://www.dependencywalker.com/ to see if your dll is even trivially loadable. At 2006/03/29 03:20 PM, Greg Chadwick wrote: >For some reason HL2 refuses to load my client.dll. It just defaults to >using the HL2DM one. It just stopped working at some point and I'm not >entirely sure why. > >I've tried putting a breakpoint on the CreateInterface function as well >as the CHLClient::Init function to see if the dll is getting loaded, and >returning an error code or something when Source tries to intialize it >and thus the HL2DM one is used instead but neither of these functions >seemed to be called. I also ran filemon from SysInternals.com while I >loaded up the mod and that shows that my client.dll is opened but it >doesn't show any read operations. It does show a query operation which >may be taking a look at the DLL exports or possibly just checking the >size I'm not sure. After than it then shows a whole load of read >activity for the HL2DM client.dll file. > >So it appears HL2 takes a look at my client.dll decides it doesn't like >it before running any code within it and then uses the HL2DM client.dll >instead. The question is why? > >Has anyone encountered this before? I do remember this happening to me >one time but IIRC a rebuild fixed it or it went away of its own accord >which doesn't seem to be happening this time. > >_______________________________________________ >To unsubscribe, edit your list preferences, or view the list archives, please visit: >http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
