MouseHookLLProc: we could have a problem!?

My x64 port of InpOut32
Post Reply
Skooma12
New User
Posts: 2
Joined: Mon Apr 23, 2018 9:53 am

MouseHookLLProc: we could have a problem!?

Post by Skooma12 » Mon Apr 23, 2018 10:28 am

]Some examples if useful information are:
1) XMBC Version (see log file) X-Mouse Button Control v2.17 (x64)
2) Windows OS & version (and if its x86/x64 if you know - see log file) Win7 sp(x64)
3) Number of mouse buttons. 5
4) What mouse driver you have installed (generic HID device or manufacturer specific) Snatdart + COUGAR_MINOS_X3_Firmware_V1.1
5) Any other mouse configuration software installed (including manufacturers software)
6) As detailed description of the problem with any relevant apps you're using that show the issue.

It was set, the wheel of a mouse wheel was turned upwards and replaced with a mouse wheel, and accept "Ignore repeated remapped horizontal scroll".

Loop error:

MouseHiikLLProc: Injected message was modified by something else therefore we coluld we have a problem!


two messages per second :shock:

Code: Select all

20-04-3918 04:12:34.144> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x025bf090)
 (Error code 997: Протекает наложенное событие ввода/вывода. )
20-04-3918 04:12:40.959> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x025bf090)
 (Error code 997: Протекает наложенное событие ввода/вывода. )
20-04-3918 04:12:45.319> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x025bf090)
 (Error code 997: Протекает наложенное событие ввода/вывода. )
20-04-3918 04:13:12.004> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x025bf090)
 (Error code 997: Протекает наложенное событие ввода/вывода. )
20-04-3918 04:13:19.820> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x025bf090)
 (Error code 997: Протекает наложенное событие ввода/вывода. )
20-04-3918 04:17:59.770> ***************************************************************************
20-04-3918 04:17:59.770> WARNING: Mouse hook has taken too long (203 ms). Hook may be disabled.
20-04-3918 04:17:59.770> MouseHookData: Msg=0x0202 (WM_LBUTTONUP), X=830, Y=465, Data=0x00000000, Flags=0x00000000, Time=24422393, Info=0x0, Ptr=0xC093B, Layer=0
20-04-3918 04:17:59.770> ***************************************************************************
20-04-3918 04:18:39.498> ***************************************************************************
20-04-3918 04:18:39.498> WARNING: Mouse hook has taken too long (202 ms). Hook may be disabled.
20-04-3918 04:18:39.498> MouseHookData: Msg=0x0202 (WM_LBUTTONUP), X=840, Y=632, Data=0x00000000, Flags=0x00000000, Time=24462111, Info=0x0, Ptr=0xD093B, Layer=0
20-04-3918 04:18:39.498> ***************************************************************************

*******************************************************************************************************************************************
21-04-3918 00:46:42.442> X-Mouse Button Control v2.17 (x64) Startup. Commandline '/notportable'
21-04-3918 00:46:42.472> Running in high integrity mode (0x00003000)
21-04-3918 00:46:42.473> Loaded 2 application specific profiles (1 normal and 1 custom window).
21-04-3918 00:46:42.473> NewApplicationSettings: SPIThread is not initialised.
21-04-3918 00:46:42.483> Running on Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit, Hook Timeout: 200 ms
21-04-3918 00:46:42.483> Warning: Low Level Hook Timeout is low. If you have problems try increasing this value.
21-04-3918 00:46:42.483> Startup folder: 'C:\Program Files\Highresolution Enterprises\X-Mouse Button Control\'
21-04-3918 00:46:42.483> Settings (and log) folder: 'C:\Users\Azure\AppData\Roaming\Highresolution Enterprises\XMouseButtonControl\'
21-04-3918 00:46:42.484> Using keyboard language 0x04190409
21-04-3918 01:00:24.914> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x02453ef0)
 (Error code 997: Протекает наложенное событие ввода/вывода. )
21-04-3918 01:00:26.887> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x02453ef0)
 (Error code 997: Протекает наложенное событие ввода/вывода. )
21-04-3918 01:01:31.366> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x02453ef0)
 (Error code 997: Протекает наложенное событие ввода/вывода. )
21-04-3918 01:01:32.249> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x02453ef0)
 (Error code 997: Протекает наложенное событие ввода/вывода. )
21-04-3918 01:01:34.521> StopQTTimer: Unable to delete QueueTimer 997 (0x00000002) as it is executing. The timer will be cleaned up when execution finishes. (0x02453ef0)
 (Error code 997: Протекает наложенное событие ввода/вывода. )

User avatar
phil
Site Admin
Posts: 5550
Joined: Sun Apr 06, 2003 11:12 pm

Re: MouseHookLLProc: we could have a problem!?

Post by phil » Mon Apr 23, 2018 10:58 am

Why two posts in the wrong (inpout32) forum?!
This is clearly meant to be an XMBC report.. .I will move one of the posts there and delete the other one - but in the future, please use the correct forum.

Now on to the problem...
You haven't really told me what the problem is... Is there actually a problem or are you just concerned about the log messages?

1. The log clip you posted does not seem to include the entry about Injected message was modified by something else therefore we could we have a problem" but all that means is another piece of software has probably hooked the mouse and changed the message that XMBC injected - it may or may not be a problem.

You mention a loop, but I can't see one - when you scroll, you will get lots of messages - but this does not mean its a loop, it may just be lots of repeated scroll messages.

2. What does concern me, is the "WARNING: Mouse hook has taken too long (203 ms). Hook may be disabled."
Why is your hook timeout soooo low (fast)? I recommend at least 500ms or 1000ms (1s). That's worth trying you can change it on the advanced settings tab - and you have to reboot to apply the change. If the hook times out while XMBC is doing its stuff, things can be left in an undetermined state. Usually the XMBC installer will increase this value automatically - so either that didn't work or you (or some other software) has changed it.

3. Can you translate "Протекает наложенное событие ввода/вывода." for me?

Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, Intel i5-6600k, Asus 170-A, 16GB DDR4,
nVidia GeForce GTX 970, 2xEvo 850 (RAID 0), 2x2TB WD Black (RAID1)

Skooma12
New User
Posts: 2
Joined: Mon Apr 23, 2018 9:53 am

Re: MouseHookLLProc: we could have a problem!?

Post by Skooma12 » Mon Apr 23, 2018 2:55 pm

Two topics in the wrong place :( Sorry, not on purpose :roll:


1.The problem is that in the game, game addon can't be installed and what it says about the mouse.(Until this week worked without problems, together with XMouse)

Code: Select all

ZO_GameMenu_InGameNavigationContainerScrollChildZO_GameMenu_ChildlessHeader1_MouseUp:3: in function '(main chunk)'
They same as the are linked? Error in the game, and spam entries in the logs of the program began simultaneously, but the cause is not know. Sometimes the mouse for a second makes over sensitivity.

Found, here is the log.

Code: Select all

23-04-3918 01:19:23.725> MouseHookLLProc: Injected message was modified by something else therefore we could have a problem!
23-04-3918 01:19:23.821> MouseHookLLProc: Injected message was modified by something else therefore we could have a problem!
23-04-3918 01:19:24.844> MouseHookLLProc: Injected message was modified by something else therefore we could have a problem!
23-04-3918 01:19:24.972> MouseHookLLProc: Injected message was modified by something else therefore we could have a problem!
23-04-3918 01:19:24.977> Removing any active XMBCHook Timers...
23-04-3918 01:19:24.978> Timer thread exited with error code 0.
23-04-3918 01:19:24.981> CSendInput: Exiting SendInput thread.
23-04-3918 01:19:24.981> HookThread: Finished cleaning up.
23-04-3918 01:19:24.981> Hook thread exited with error code 0.
23-04-3918 01:22:07.727> CMyMessageWnd::OnSetup   -   Opening setup dialog.
23-04-3918 01:22:07.740> Loaded 2 application specific profiles (1 normal and 1 custom window).
23-04-3918 01:22:50.395> Applying changes to X-Mouse Button Control settings...
23-04-3918 01:22:50.399> Loaded 2 application specific profiles (1 normal and 1 custom window).
23-04-3918 01:22:50.399> NewApplicationSettings: SPIThread is not initialised.
23-04-3918 01:22:53.510> Loaded 2 application specific profiles (1 normal and 1 custom window).
23-04-3918 01:22:53.510> NewApplicationSettings: SPIThread is not initialised.
23-04-3918 01:22:53.510> Using keyboard language 0x04190409
23-04-3918 01:26:38.794> Applying changes to X-Mouse Button Control settings...
23-04-3918 01:26:38.798> Loaded 2 application specific profiles (1 normal and 1 custom window).
23-04-3918 01:26:44.087> CMyMessageWnd::OnSetup   -   Setup dialog closed.
23-04-3918 01:26:44.091> Loaded 2 application specific profiles (1 normal and 1 custom window).
23-04-3918 01:26:48.204> Exit requested by the user.
23-04-3918 01:26:48.211> Removing any active XMBCHook Timers...
23-04-3918 01:26:48.211> Timer thread exited with error code 0.
23-04-3918 01:26:48.212> CSendInput: Exiting SendInput thread.
23-04-3918 01:26:48.212> HookThread: Finished cleaning up.
23-04-3918 01:26:48.212> Hook thread exited with error code 0.
23-04-3918 01:26:48.212> X-Mouse Button Control Shutdown.


2.Hook timeout will correct. When the test changed the default value of the forgotten. Thanks. :|


3.Run overlay Input\ouput event.

MB try to switch usb port mouse\Keyboard?

More immediately, the question of how to implement best. I read somewhere that the wheels are no events up. Because of this, there are difficulties.
I want: Wheel up sends only one event.(Same-Wheel up, or any other keyboard or mouse key)


Thanks!

Post Reply