PocketMatrix

The easiest way to handle this is to make all your paths relative to the location of the main program EXE. That way you aren't hardcoding your paths (which is bad for many reasons - Storage Card installs, non-english devices, etc). You can use GetModuleFileName to get the path and filename of the current running exe. Extract the path, and slap it on the beginning of all the files you need to load.

Dan East

That's just the debugger asking for a local, debug version of the DLL. If you provide a debug version (MS didn't provide a debug version of gx.dll, so you can't for that DLL) then you could step into the DLL and debug just like with your app. MS does provide debug versions of some DLLs such as MFC, etc.

Dan East

so I cdan never get rid of that notice about gx.dll

how come MS does not provide a debug version anyways?

since I have a XSCALE the only way to take advantage of it is write assembly.. or could someone write a library and then I could use that?

There should be two different ways to remedy that. First you can extract gx.dll to your PC somewhere, and when it asks for the dll browse and select it (make sure you use the gx.dll to match your processor type). It still may warn you that gx.dll does not contain debugging info, but I don't think it will say that every time you start a debug session.

Second, if you go into the Project Settings, "Debug" tab, and select "Additional DLLs" you will see an option "Try to locate other DLLs". Try unchecking that option.

There's really no need for a debug version of gx.dll. That library does very little, and more importantly, does not do extensive calling into other libraries. Some libraries, like MFC.dll, are pretty complex and make calls into user code, so it is very important that debug versions are provided so the entire call stack can be navigated.

Dan East