Re: (Apparent) inability of DirectX to initialize DLL's at run-time

From: The March Hare (MVP) (phil_at_ndsm.maps)
Date: 07/15/04


Date: Wed, 14 Jul 2004 23:43:48 -0600

On Wed, 14 Jul 2004 17:22:02 -0700,
LostonInternetSuperhighway@discussions.microsoft.com wrote:

> I'm attempting to compile and run a "hello world" code sample from a third-party introductory programming book. The code contains a simple windowing interface, which it references once, and a simple DirectX interface with which it (supposedly) writes a rectangular pattern to the window it creates. When compiled and executed, the program dies (commits an access violation that gets it busted by
> the operating system with the familiar "This program has performed an illegal operation and will be shut down") at various unassuming places in the code, depending on what trivial changes are made to the code, and pops up "Loaded 'C:\WINDOWS\SYSTEM\[XXXXXXXX].DLL', no matching symbolic information found" messages upon entering 'main' at the beginning of each debug execution. I am running Windows 98 (recently installed), just installed (or rather, ran the installers of, hard for me to trust installation proceeded appropriately and completely like the damn installers indicate-- one or both of the installers may have happened to have run into the "disk full" limit during installation, but were re-run in each instance when appropriate memory was allocated) DirectX 9.0 and its SDK, and am compiling, executing, and debugging using Visual C++ 6.0. The following DLL's are cited as lacking "matching symbolic information":
>
> NTDLL.DLL
> DDRAW.DLL
> VERSION.DLL
> ADVAPI32.DLL
> GDI32.DLL
> KERNEL32.DLL
> USER32.DLL
> D3D8.DLL
>
> What gives? Could it be a problem with the DirectX? It's SDK? The libraries? The example code I'm trying to compile and run? Is my operating system screwed up? Could anyone reading this drop me any hints?

This has been answered in ../graphics.

Please don't multi-post.

-- 
1.  If there are questions above, please answer them in-line.  In any case,
don't top post. (Otherwise, don't expect a followup) See
http://tinyurl.com/22ubu
2.  Remove this signature from your response if your newsreader isn't
intelligent enough to do it.
3.  Common courtesy is to followup if someone helped you or if you found a
solution on your own.


Relevant Pages

  • (Apparent) inability of DirectX to initialize DLLs at run-time
    ... Could it be a problem with the DirectX? ... It's SDK? ... The libraries? ... The example code I'm trying to compile and run? ...
    (microsoft.public.win32.programmer.directx.video)
  • (Apparent) failure of DirectX to initialize DLLs at run-time
    ... Could it be a problem with the DirectX? ... It's SDK? ... The libraries? ... The example code I'm trying to compile and run? ...
    (microsoft.public.win32.programmer.directx.graphics)
  • Re: DirectX 9.1 beta out with DirectShow.Net???
    ... [Please do not mail me a copy of your followup] ... There is no DirectX 9.1. ... The most current SDK ... "The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ: ...
    (microsoft.public.win32.programmer.directx.managed)
  • Re: DirectX 9.1 beta out with DirectShow.Net???
    ... [Please do not mail me a copy of your followup] ... There is no DirectX 9.1. ... The most current SDK ... "The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ: ...
    (microsoft.public.win32.programmer.directx.video)
  • Re: Directx and ScreensaverProc
    ... [Please do not mail me a copy of your followup] ... >That was in the DirectX 8 SDK, I don't think it's in the current SDK. ... Prev by Date: ...
    (microsoft.public.win32.programmer.directx.graphics)