ddentry10 could not be located in ddraw.dll *boggle*Follow

I get this error every time I try to run Everquest (after the patch loads) - "The procedure entry point DdEntry10 could not be located in the dynamic link library DDRAW.dll."

Processor type/speed: AMD Athlon(tm) 64 Processor 3400+, MMX, 3DNow, ~2.2GHz
Total Hard drive space/Free hard drive space:
Amount of Ram: 1024MB RAM
Video card type: NVIDIA GeForce FX5200
Operating system: Windows XP
DirectX Version: DirectX 9.0b (4.09.0000.0902)
frequency of problem: every time I try to run Everquest


Contents of debug.txt file ...


[Registration Servers]
{
"NT-dsauter:5999"
}
[Login Servers]
{
"NT-dsauter:15900"
"NT-dsauter:15901"
"NT-dsauter:15902"
"NT-dsauter:15903"
}




Edited, Wed Mar 24 21:57:40 2004 by hokkeypuck

Edited, Wed Mar 24 22:36:12 2004 by hokkeypuck

Tried that a couple of times - no success. Any other suggestions?

Thanks for trying. I'll wait and see.

Edited, Wed Mar 24 22:57:38 2004 by hokkeypuck

So I reinstalled Windows and this is still happening. AARGGH!

Are you running as a computer administrator account on xp?

i reformated and reinstalled windows, and still no luck.

Wild goose chases Kao has sent posters on: Hundreds.

Number of problems Smash has suggeted taking action on: 3.

Number of solutions: 3.

Were it a contest between volume and accuracy, I'd go with accuracy personally.

That being said, Kao certainly attempts to solve a hundred times the issues I do. The percentage of those that acutally get fixed, who knows, but he tries and there's something to be said for that alone.

I have this foolish qualm about not taking random guesses if I have no idea what the problem's related to. I mean, since formatting and re-installing didn't work, maybe you can shake a witchdoctor's rattle around the machine and pray to the appropriate voodoo god.

That might just do the trick.

One of you guys or both, post your dxdiag report, and we'll see if we can't figure out what's up.

Start
Run
type dxdiag
A directx diagnostic tool will pop up. Click yes or no to check for WHQL signatures, it wont matter to m eeither way,
Click on "save all information"
Save the text dump file somewhere.
Edit any incriminating information and cut and paste the rest here.

It's 99 percent likely that it's on Sony's end, but it'd be nice to have a look anyway and see if there's anything obvious.

Or you could fromat and reinstall windows again, up to you :)

30's fine, I'll take your word for it. You've only sent 30 people on wild goose chases.

Look, I don't care, really. You help a lot of people out, that's commendable. I just wish when you had no idea at all you'd just post "I have no idea at all." Instead of wasting people's time.