RUNDLL.EXE Entry point not found?

Discussions about anything Computer Hardware Related. Overclocking, underclocking and talk about the latest or even the oldest technology. PCA Reviews feedback
Post Reply
User avatar
FanTum
Golden Member
Posts: 989
Joined: Thu Nov 23, 2000 2:40 pm
Location: Sarnia, Ontario

RUNDLL.EXE Entry point not found?

Post by FanTum »

All of a sudden i get the above message and- "The procedure entry point ThunkConnect could not be located in the dynamic link library Kernell 32.dll. " After boot up and when i click on advanced properties for display settings.

Latest thing I've done is unistalled Diablo 2, and installed the latest NVIDIA drivers.

Any suggestions please?
Image
"This is my Kung Fu, and it is strong!"
User avatar
FlyingPenguin
Flightless Bird
Posts: 33162
Joined: Wed Nov 22, 2000 11:13 am
Location: Central Florida
Contact:

Post by FlyingPenguin »

The new 40 NVidia drivers are a beta. Although no one's reported problems with them (except that the refresh rate fix doesn't work with it) I would recommend going back to the 30.x driver for now until the driver is official.
---
“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez

Image
User avatar
FanTum
Golden Member
Posts: 989
Joined: Thu Nov 23, 2000 2:40 pm
Location: Sarnia, Ontario

Post by FanTum »

Somethin still isn't right!!!!

Still gettn' the same error report!
Image
"This is my Kung Fu, and it is strong!"
User avatar
Lmandrake
Posts: 1513
Joined: Wed Nov 22, 2000 11:03 am
Location: Millersville, MD

Post by Lmandrake »

I think your problem is related to the drivers used for importing images from scanners etc. Find all instances of twain.dll and twain32.dll and rename them to twain.old and twain32.old and then replace them with newer versions. You can find them on the net.... If that does not work, search for all dlls with "thunk" in them and try replacing those...
User avatar
FanTum
Golden Member
Posts: 989
Joined: Thu Nov 23, 2000 2:40 pm
Location: Sarnia, Ontario

Post by FanTum »

Fixed it!!

I had to go back two denonator installs to 29.42 to make the error go away!!

Anyone had other problems with the new detonators?

Runnin' a G-Force 4 TI4400.
Image
"This is my Kung Fu, and it is strong!"
Post Reply