Hotkeys not working/certain keys not working

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

mikelhall
GamingTools Subscriber
Posts: 13
Joined: Wed Jun 29, 2005 1:02 pm

Hotkeys not working/certain keys not working

Post by mikelhall » Sat Jul 23, 2005 7:50 am

I have a strange problem and its beginning to really aggravate me. I'm using WinEQ2, and I'm running 2 instances of EQ1.

The problem I have is that at least a couple of times an hour...they alpha keys that are mapped to any WinEQ2 hotkeys stop working. IE, z, o, p etc will not work. I have to switch into the next instance and back again for them to work.

Sometimes, they will actually start working like I'm holding down the CTRL+ALT key with them! Its getting frustration that I can type in raid without either missing letters or my PiP dissapearing or my screen shrinking etc..

Is there anyway to stop this from happening?

Thanks

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sat Jul 23, 2005 9:45 am

It sounds like keys are simply getting stuck down (not on your keyboard, just to WinEQ) for some reason. This issue hasnt been reported in many months, at least not with any response after I ask questions about it, so I've assumed this wasnt an issue anymore. You really only need to tap the ctrl and alt keys to fix it, but the problem needs to get fixed if it's still there. It wont be an issue in WinEQ 3, but that's a few months off ;)

The keys can ONLY get stuck down when you switch sessions. So here's what I need to know
1) What WinEQ hotkeys do you use (preferably the ones right before you have this problem, not ones rarely used), and what keys are they set to?
2) How do you switch sessions? Out of click, alt+tab, wineq next/last hotkeys, global activation keys, which do you use before this problem happens?

That's about it. It sounds like you use a hotkey involving CTRL+ALT to switch sessions, which could be a few different ones, but I need to know what exactly happens before you get this problem.

mikelhall
GamingTools Subscriber
Posts: 13
Joined: Wed Jun 29, 2005 1:02 pm

Post by mikelhall » Sun Jul 24, 2005 8:29 am

I use CTRL+ALT+1 for session 1, and CTRL+ALT+2 for session 2.

I use a Saitek Command Pad for the switching, I have those commands mapped to a button each on that.

Also, this doesnt happen 'right' after switching sessions, it happens during a session with keys were previously working correctly. I can type a full sentance with all letters in it, then hit enter. The next thing I type will be missing the 'hotkey' text, such as z, m etc...switching sessions will then fix it.

Also, I tried to change the hotkeys in WinEQ to other keys, but the same letters still get stuck. I WISH there was a way to completely remove the hotkey setting for things you dont want to use HINT HINT..lol

Thanks for your help!

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sun Jul 24, 2005 9:25 am

There is. You can set them to NONE.

It doesnt make sense that the keys would get stuck at any other time than switching sessions... It sounds like it might have something to do with that saitek though.

mikelhall
GamingTools Subscriber
Posts: 13
Joined: Wed Jun 29, 2005 1:02 pm

Post by mikelhall » Sun Jul 24, 2005 2:20 pm

I used the Saitek before WinEQ, with other keys bound to it in EQ and it was always worked fine. I also use it in WoW without any problems..

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sun Jul 24, 2005 2:24 pm

Yes, I'm just saying that it may be a problem with the Saitek in WinEQ, not with the games. I ordered one and will be able to test with one in a few days.

mikelhall
GamingTools Subscriber
Posts: 13
Joined: Wed Jun 29, 2005 1:02 pm

Post by mikelhall » Mon Jul 25, 2005 10:11 am

Wow, thanks

For more clarification, I set my other hotkeys to NONE and it has helped things, namely getting stuck in odd window sizes, or PiP problems, but I still have some stuck alpha characters.

I will watch the problem and try to give as accurate a listing as possible.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed Jul 27, 2005 6:57 pm

Ok, my Saitek is here. I will be testing this within a day or two

mikelhall
GamingTools Subscriber
Posts: 13
Joined: Wed Jun 29, 2005 1:02 pm

Post by mikelhall » Wed Jul 27, 2005 10:16 pm

Well, I tried it again.

It most definately happens after being able to type for a bit, not right after a session switch. But it does happen only in a new series of inputs. IE, it will not in the same sentance allow me to type n and then perform the WinEQ function associated in some form with the letter n. It will do it the first time a letter is typed in a new input. It will also do it no matter what the modifier keys for the input letter is. If I am using Ctrl+alt+n, it will occur if I enter 'n' or 'N'. The only way to stop it is to remove any key binds that have alpha characters from the WinEQ preferences.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed Jul 27, 2005 10:26 pm

Interesting.

Let me ask you this, out of curiosity. Do you ever use the right ctrl/alt/shift/win keys?

Also, can you enable the memory indicator for testing this? The indicator will show "C A W S" to indicate if it thinks modifiers are pressed. I would like to know if these appear on when you have the problem

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Thu Jul 28, 2005 2:08 am

Can you share with me your command pad profile? I want to try to replicate your settings as closely as possible. Leave out any private settings or buttons you dont use if you want

mikelhall
GamingTools Subscriber
Posts: 13
Joined: Wed Jun 29, 2005 1:02 pm

Post by mikelhall » Thu Jul 28, 2005 8:07 am

Sure, I have 8 mapped to CTRL+ALT+1, and 9 mapped to CTRL+ALT+2

That is all.

In WinEQ preferences, in have set to NONE all extraneous commands such as switch sessions, Lock PiP ETC.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sat Jul 30, 2005 8:34 am

Hmmm... no matter what I do, I cant make this happen.

Post SysInfo.txt for me

mikelhall
GamingTools Subscriber
Posts: 13
Joined: Wed Jun 29, 2005 1:02 pm

Post by mikelhall » Sat Jul 30, 2005 12:32 pm

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
System Physical RAM: 851/1535MB
Page File: 2431/2916MB
Virtual Memory: 1918/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) XP 3000+ @ 2171MHz
Video 1: \\.\DISPLAY1/NVIDIA GeForce 6800
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Sound: NVIDIA(R) nForce(TM) Audio
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.08

Loaded Modules:
-----------------------------------
Module 0: C:\Program Files\Sony\EverQuest\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: C:\Program Files\Sony\EverQuest\mss32.dll
Module 4: C:\WINDOWS\system32\USER32.dll
Module 5: C:\WINDOWS\system32\GDI32.dll
Module 6: C:\WINDOWS\system32\WINMM.dll
Module 7: C:\WINDOWS\system32\ADVAPI32.dll
Module 8: C:\WINDOWS\system32\RPCRT4.dll
Module 9: C:\WINDOWS\system32\WSOCK32.dll
Module 10: C:\WINDOWS\system32\WS2_32.dll
Module 11: C:\WINDOWS\system32\msvcrt.dll
Module 12: C:\WINDOWS\system32\WS2HELP.dll
Module 13: C:\WINDOWS\system32\DINPUT8.dll
Module 14: C:\WINDOWS\system32\IMM32.dll
Module 15: C:\Program Files\Sony\EverQuest\DSETUP.dll
Module 16: C:\WINDOWS\system32\VERSION.dll
Module 17: C:\WINDOWS\system32\ole32.dll
Module 18: C:\WINDOWS\system32\SHELL32.dll
Module 19: C:\WINDOWS\system32\SHLWAPI.dll
Module 20: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 21: C:\WINDOWS\system32\comctl32.dll
Module 22: C:\Program Files\WinEQ2\WinEQ2.dll
Module 23: C:\WINDOWS\Lavish.dll
Module 24: C:\WINDOWS\system32\PSAPI.DLL
Module 25: C:\Program Files\WinEQ2\WinEQ2-EQ.dll
Module 26: C:\WINDOWS\system32\MSIMG32.dll
Module 27: C:\Program Files\WinEQ2\WinEQ2-D3D9.dll
Module 28: C:\Program Files\WinEQ2\WinEQ2-D3D8.dll
Module 29: C:\Program Files\WinEQ2\WinEQ2-DI8.dll
Module 30: C:\WINDOWS\system32\mswsock.dll
Module 31: C:\WINDOWS\system32\hnetcfg.dll
Module 32: C:\WINDOWS\System32\wshtcpip.dll
Module 33: C:\WINDOWS\system32\DNSAPI.dll
Module 34: C:\WINDOWS\System32\winrnr.dll
Module 35: C:\WINDOWS\system32\WLDAP32.dll
Module 36: C:\WINDOWS\system32\rasadhlp.dll
Module 37: C:\WINDOWS\system32\uxtheme.dll
Module 38: C:\Program Files\WinEQ2\EQPlayNice.dll
Module 39: C:\DOCUME~1\MICHAE~1\LOCALS~1\Temp\IadHide5.dll
Module 40: C:\WINDOWS\System32\dwspy36.DLL
Module 41: C:\WINDOWS\system32\OLEAUT32.dll
Module 42: C:\WINDOWS\system32\NTMARTA.DLL
Module 43: C:\WINDOWS\system32\SAMLIB.dll
Module 44: C:\Program Files\Sony\EverQuest\EQGraphicsDX9.DLL
Module 45: C:\WINDOWS\system32\d3d9.dll
Module 46: C:\WINDOWS\system32\d3d8thk.dll
Module 47: C:\Program Files\Sony\EverQuest\dpvs.dll
Module 48: C:\Program Files\Microsoft Hardware\Mouse\MSH_ZWF.dll
Module 49: C:\WINDOWS\system32\HID.DLL
Module 50: C:\WINDOWS\system32\SETUPAPI.DLL
Module 51: C:\WINDOWS\system32\WINTRUST.dll
Module 52: C:\WINDOWS\system32\CRYPT32.dll
Module 53: C:\WINDOWS\system32\MSASN1.dll
Module 54: C:\WINDOWS\system32\IMAGEHLP.dll
Module 55: C:\Program Files\Sony\EverQuest\mssmp3.asi
Module 56: C:\Program Files\Sony\EverQuest\mssvoice.asi
Module 57: C:\Program Files\Sony\EverQuest\mssa3d.m3d
Module 58: C:\Program Files\Sony\EverQuest\mssds3d.m3d
Module 59: C:\Program Files\Sony\EverQuest\mssdx7.m3d
Module 60: C:\Program Files\Sony\EverQuest\msseax.m3d
Module 61: C:\Program Files\Sony\EverQuest\mssrsx.m3d
Module 62: C:\WINDOWS\system32\MSACM32.dll
Module 63: C:\Program Files\Sony\EverQuest\msssoft.m3d
Module 64: C:\Program Files\Sony\EverQuest\mssdsp.flt
Module 65: C:\WINDOWS\system32\wdmaud.drv
Module 66: C:\WINDOWS\system32\msacm32.drv
Module 67: C:\WINDOWS\system32\midimap.dll
Module 68: C:\WINDOWS\system32\DSOUND.DLL
Module 69: C:\WINDOWS\system32\KsUser.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce 6800/nv4_disp.dll/6/14/10/7776
Adapter Display Mode: 1280x1024 D3DFMT_X8R8G8B8
Game Display Mode: 1280x1024 D3DFMT_X8R8G8B8
Current Adapter: 0
Available Texture Memory: 213MB
Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
DirectInput8:
-----------------------------------

EverQuest:
-----------------------------------
Profile 1: Hriis
EQ Path: C:\Program Files\Sony\EverQuest
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 29 (+145 min RAM)
Texture Compression: ON (+0 min RAM)
MipMapping: ON (+4 min RAM)
Sound: ON (+22 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Quality: HIGH (+32 min RAM)
Sky: COMPLEX (+10 min RAM)
Calculated minimum RAM: 500MB (BASE+217MB)
Level of Detail: 1
MaxFPS: 100
Additional setting: HardwareTnL=FALSE
Additional setting: VSync=1
Additional setting: VertexShaders=0
Additional setting: 20PixelShaders=0
Additional setting: 1xPixelShaders=0

EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Jul 6 2005 17:48:42
Foreground
Mode: FPS Limiter
Max FPS: 40
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 30
Rendering: 1/30

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Sat Jul 30, 2005 12:43 pm

Module 40: C:\WINDOWS\System32\dwspy36.DLL
Do you know what ENZEC is? It seems pretty obscure so I'm assuming you dont, and even if you did, I dont know why it would appear in the EQ process. I can only assume this is the spyware/keylogger version of the file.

This type of spyware WOULD interfere with WinEQ and is probably the real problem here.

I highly recommend downloading and using Microsoft Anti-Spyware http://www.microsoft.com/downloads/deta ... laylang=en

Post Reply