|
|||||||
 |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
02-05-2004, 10:02 AM
|
#1 |
|
Member (10 bit)
Join Date: Mar 2002
Location: Buffalo NY
Posts: 512
|
'Entry Point Not Found' error message
I get 2 error messages when I try to run DX Diag as follows:
Entry Point not Found The procedure entry point GetRawInputDeviceInfoW can't be located in USER32.dll and: Entry Point not Found Procedure entry point DdEntry1 can't be found in GDI32.dll No other errors show. I also got the first error while trying to run a demo program for a HDTV tuner card's software. I'm running 2k w/sp4 using DirectX V9 I have also did a 'upgrade' of 2k for another problem that was resolved per M$'s recomemdation. I don't know if these two problems were there before the 'upgrade'! Any ideas?? |
|
|
|
02-05-2004, 01:48 PM
|
#2 |
|
Member (9 bit)
Join Date: Oct 1999
Posts: 406
|
I seriously think the demo program is the culprit. Trying to find USER32.dll and GDI32.dll.
And I quote, "This is a Windows 2000 Executive STATUS error message. Choose one of the options from the message box. You may have to reinstall the dynamic-link library or contact its supplier." Try uninstalling the demo prog. |
|
|
|
|
02-05-2004, 02:00 PM
|
#3 |
|
Professional gadfly
Join Date: Jan 2002
Location: Minneapolis, MN
Posts: 6,364
 |
I also think the DLLs are screwed up. Uninstalling the demo program may not fix everything, though. If the DLLs have been overwritten, you are going to have to reinstall DirectX.
|
|
|
|
|
02-06-2004, 08:17 AM
|
#4 |
|
Member (10 bit)
Join Date: Mar 2002
Location: Buffalo NY
Posts: 512
|
I don't know if it was the demo program that did it. I got errors when it was installed (don't remember what they were). I only noticed it when I tried to run the program, then noticed it using DX Diag.
I did re-install Direct X 9 and all seems fine. Just what do these 'entry points' mean?? |
|
|
|
|
02-06-2004, 08:56 AM
|
#5 |
|
Professional gadfly
Join Date: Jan 2002
Location: Minneapolis, MN
Posts: 6,364
|
DLLs contain functions that are called by other programs when they are needed (that's the whole "dynamically loaded" thing: these functions aren't loaded into memory until they are called). However, when a program calls a function from a DLL, it needs to know where that function is and how to call it. If it can't find it, there are problems.
That's a vastly simplified version of the answer, but it's close enough. |
|
|
|
|
02-06-2004, 09:10 AM
|
#6 |
|
Member (10 bit)
Join Date: Mar 2002
Location: Buffalo NY
Posts: 512
|
It is the 'entry point' to the DLL or the 'entry point' to the other app that was in question?
|
|
|
|
|
02-06-2004, 09:15 AM
|
#7 |
|
Professional gadfly
Join Date: Jan 2002
Location: Minneapolis, MN
Posts: 6,364
|
It's the entry points in the DLL that were in question. That's why the DLLs were listed in the error message, and why replacing the DLLs when you reinstalled DirectX fixed the problem.
Regular executables don't have entry points like DLLs, they have something else. |
|
|
|
|
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Linear Mode
