A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » Motherboards » Asus Motherboards
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

trouble with keyhook.exe



 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1  
Old March 7th 08, 03:09 AM posted to alt.comp.periphs.mainboard.asus
nesredep egrob
external usenet poster
 
Posts: 2
Default trouble with keyhook.exe

I have set up a P5S-MX SE mother board. Everything has gone well except I am
left with a message:
"The procedure entry point ?DDrawSupportGetDriverName@CSiSEsc@@AEHPAD@Z could
not be located in the dynamic link library SiSApCom.dll"

For that reason I have run the MB drivers and applications CD several times
thinking that something is wrong there - all to no avail-

Does anyone have an answer to that, Please

Borge in sunny Perth, Australia
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Trouble with wireless connection. Would appreciate suggestions on where to trouble shoot or where to look for problems. Ronald Homebuilt PC's 2 September 24th 07 11:54 AM
AMD in trouble chrisv General 3 May 17th 07 04:11 AM
CD-RW Trouble RH710 General 7 September 21st 04 04:45 AM
trouble with old 486 Francois General 13 April 21st 04 12:37 AM
ATI is in trouble J.Clarke Nvidia Videocards 38 December 11th 03 01:56 AM


All times are GMT +1. The time now is 09:32 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.