Keep getting wierd key-mapping's?!?!

http://www.privatepaste.com/d13f16c886

Just started dualboxing and I keep getting same promlem. Out of the blue I get wierd key-mapping's or re-mapping, where a key or a group of key's get's re-mapped, like ` will go from just that to somthing like "v". 1,2,3 some times will turn into r,t,y "Q" to "L" etc. Most recently when I swap between screen's "f12" is pressed on my main client but only when switching screens like on auto or somthing,lol?!?! also when I try and configure anyother key other then 1/= to "interact with target" there is lag and or re-mapping error's,... Don't know if I missed somthing in the setup but I'm kinda stuck. So if anyone could help I would me most appreciative.

P.S. Already tried re-instaling about 3 times. Everytime the re-mapping would get to be to much. Becuase at the beggining it would only be one or two thing but with a little use I would have wound up with up 7 key's when pressed not giving the correct values when pressed. on either client unless keymaping was of so "q" would be ` no matter what unless keymaping weren't disabled. re-instealed each time to get fresh mappings wierd thing is this would be on all characters and config's?!?!?!!?

[lax]

This is more likely to be a conflict with your keyboard region setting, or keyboard configuration software, or some other software operating on your PC at the time. Your ISBoxer settings of course do not include these re-mappings, so no amount of reinstalling it will be expected to affect this issue


You can get me some diagnostic information that might provide a hint. In the ISBoxer Help menu select "Diagnostics for game crashes" -- yes I know it's not crashing, but instead of seeing the wrong keys being sent, just pretend it crashed at that point, and follow the instructions to get me these diagnostics. When generates the diagnostics it will do a "Copy", which you can just paste to me here if you like.

Ok, well mybe it's somthing obvious I'm not getting. Though now one of my clients has become completely unresponsive to most key mappings, although they are enabled. Where toon(2) cant get any other toon to fallow him or invite to group, but ctrl+alt+shift+G works just fine. Other toon(1) works just fine other toons auto follows on switch and everything?!?! Tried to reinstall again 4th time, now tried to make this other account(2) "slot 1". Thought maybe making a new team would help which did not work. So I did the wipe and reinstall. Made this other (account2) "slot 1" from start only team saved and exported, yet still the only one that auto fallow's(account1) which is now slot 2 also get's other toons to follow on alt+f.
[Basically the account I'v have been using to lead the team can't fallow?!?!]

Don't mean to whine about this but I can't understand how it worked for all this past week, made it to lvl45 and now all this?!!??! can barly use isboxer at all anymore, getting ready to make the switch to pwnboxer but there has to be a reason why this is the better software, Is it just me or does it feal like your getting broken software that you have the expertise in the field to fix it and use?! It might just be me and my setup: sandy bridge i7 extream w/ win7. or my Noobness to this whole ordeal,. but if someon could help me make the most of isboxer. Becuase right now I'm not sure if this realy be the software for me!?


As of now keymapping only works on one character which isnt real dualboxing, not trying to be a pian just Need some help!!!!!!! xdddddd


ISBoxer Diagnostics Report generated 9/5/2012 4:48 PM by ISBoxer 40.4.902.1

Running processes:
1. Agent - Process ID: 1104 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
2. Agent - Process ID: 1328 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
3. Agent - Process ID: 196 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
4. Agent - Process ID: 2028 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
5. Agent - Process ID: 2168 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
6. Agent - Process ID: 2252 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
7. Agent - Process ID: 2400 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
8. Agent - Process ID: 2732 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
9. Agent - Process ID: 3332 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
10. Agent - Process ID: 3960 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
11. Agent - Process ID: 4076 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
12. Agent - Process ID: 4108 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
13. Agent - Process ID: 4252 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
14. Agent - Process ID: 4264 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
15. Agent - Process ID: 4372 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
16. Agent - Process ID: 4500 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
17. Agent - Process ID: 4604 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
18. Agent - Process ID: 4740 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
19. Agent - Process ID: 4868 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
20. Agent - Process ID: 4904 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
21. Agent - Process ID: 5100 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
22. Agent - Process ID: 5112 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
23. Agent - Process ID: 5136 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
24. Agent - Process ID: 5224 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
25. Agent - Process ID: 5388 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
26. Agent - Process ID: 5488 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
27. Agent - Process ID: 5560 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
28. Agent - Process ID: 5632 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
29. Agent - Process ID: 5728 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
30. Agent - Process ID: 5916 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
31. Agent - Process ID: 604 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
32. Agent - Process ID: 6264 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
33. Agent - Process ID: 6420 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
34. Agent - Process ID: 6448 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
35. Agent - Process ID: 6644 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
36. Agent - Process ID: 6828 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
37. Agent - Process ID: 6976 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
38. Agent - Process ID: 7020 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
39. Agent - Process ID: 7244 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
40. Agent - Process ID: 7348 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
41. Agent - Process ID: 7428 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
42. Agent - Process ID: 7616 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
43. Agent - Process ID: 7796 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
44. Agent - Process ID: 7812 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
45. Agent - Process ID: 8076 (C:\ProgramData\Battle.net\Agent\Agent.1267\Agent.exe)
46. AlarmClock - Process ID: 2308 (C:\Program Files (x86)\GIGABYTE\Smart6\Timelock\AlarmClock.exe)
47. armsvc - Process ID: 1472 (C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\armsvc.exe)
48. audiodg - Process ID: 5016
49. chrome - Process ID: 2800 (C:\Users\Battle Groundz\AppData\Local\Google\Chrome\Application\chrome.exe)
50. chrome - Process ID: 3088 (C:\Users\Battle Groundz\AppData\Local\Google\Chrome\Application\chrome.exe)
51. chrome - Process ID: 3220 (C:\Users\Battle Groundz\AppData\Local\Google\Chrome\Application\chrome.exe)
52. chrome - Process ID: 3524 (C:\Users\Battle Groundz\AppData\Local\Google\Chrome\Application\chrome.exe)
53. chrome - Process ID: 4064 (C:\Users\Battle Groundz\AppData\Local\Google\Chrome\Application\chrome.exe)
54. chrome - Process ID: 5420 (C:\Users\Battle Groundz\AppData\Local\Google\Chrome\Application\chrome.exe)
55. chrome - Process ID: 6088 (C:\Users\Battle Groundz\AppData\Local\Google\Chrome\Application\chrome.exe)
56. chrome - Process ID: 7724 (C:\Users\Battle Groundz\AppData\Local\Google\Chrome\Application\chrome.exe)
57. chrome - Process ID: 7892 (C:\Users\Battle Groundz\AppData\Local\Google\Chrome\Application\chrome.exe)
58. conhost - Process ID: 1164
59. conhost - Process ID: 2108
60. conhost - Process ID: 2144
61. conhost - Process ID: 2264
62. conhost - Process ID: 236
63. conhost - Process ID: 2576
64. conhost - Process ID: 2828
65. conhost - Process ID: 2872
66. conhost - Process ID: 3792
67. conhost - Process ID: 3812
68. conhost - Process ID: 3892
69. conhost - Process ID: 3928
70. conhost - Process ID: 4116
71. conhost - Process ID: 4228
72. conhost - Process ID: 4272
73. conhost - Process ID: 4412
74. conhost - Process ID: 4476
75. conhost - Process ID: 4508
76. conhost - Process ID: 4748
77. conhost - Process ID: 4912
78. conhost - Process ID: 5012
79. conhost - Process ID: 5064
80. conhost - Process ID: 5108
81. conhost - Process ID: 5232
82. conhost - Process ID: 5396
83. conhost - Process ID: 5568
84. conhost - Process ID: 5692
85. conhost - Process ID: 5736
86. conhost - Process ID: 5924
87. conhost - Process ID: 6120
88. conhost - Process ID: 6272
89. conhost - Process ID: 6352
90. conhost - Process ID: 6456
91. conhost - Process ID: 6616
92. conhost - Process ID: 6652
93. conhost - Process ID: 6836
94. conhost - Process ID: 6944
95. conhost - Process ID: 6980
96. conhost - Process ID: 700
97. conhost - Process ID: 7024
98. conhost - Process ID: 7252
99. conhost - Process ID: 7436
100. conhost - Process ID: 7628
101. conhost - Process ID: 7820
102. conhost - Process ID: 7940
103. csrss - Process ID: 452
104. csrss - Process ID: 776
105. dwm - Process ID: 2232
106. explorer - Process ID: 2292
107. hkcmd - Process ID: 2940
108. igfxpers - Process ID: 2948
109. igfxtray - Process ID: 2932
110. InnerSpace - Process ID: 3940 (C:\Program Files\InnerSpace\InnerSpace.exe)
111. ISBoxer Toolkit - Process ID: 6992 (C:\Program Files\InnerSpace\ISBoxer Toolkit.exe)
112. LMS - Process ID: 2556 (C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\LMS\LMS.exe)
113. lsass - Process ID: 860
114. lsm - Process ID: 872
115. RAVCpl64 - Process ID: 2976
116. RPMDaemon - Process ID: 2744
117. SearchIndexer - Process ID: 2620
118. services - Process ID: 808
119. smss - Process ID: 304
120. SMSvcHost - Process ID: 1536
121. spoolsv - Process ID: 1348
122. SSScheduler - Process ID: 2204 (C:\Program Files (x86)\McAfee Security Scan\3.0.207\SSScheduler.exe)
123. svchost - Process ID: 1060
124. svchost - Process ID: 1376
125. svchost - Process ID: 1492
126. svchost - Process ID: 1696
127. svchost - Process ID: 2100
128. svchost - Process ID: 2904
129. svchost - Process ID: 316
130. svchost - Process ID: 3440
131. svchost - Process ID: 444
132. svchost - Process ID: 520
133. svchost - Process ID: 572
134. svchost - Process ID: 584
135. svchost - Process ID: 5928
136. svchost - Process ID: 992
137. System - Process ID: 4
138. taskhost - Process ID: 2124
139. TimeMgmtDaemon - Process ID: 1664 (C:\Program Files (x86)\GIGABYTE\Smart6\Timelock\TimeMgmtDaemon.exe)
140. TSVNCache - Process ID: 3040
141. UNS - Process ID: 3576 (C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\UNS\UNS.exe)
142. wininit - Process ID: 748
143. winlogon - Process ID: 852
144. wmpnetwk - Process ID: 2540
145. Wow-64 - Process ID: 760


Modules loaded by Wow-64 - Process ID: 760:

[lax]

Is it just me or does it feal like your getting broken software that you have the expertise in the field to fix it and use?

Umm.. well, nobody has ever come here and said with a confused look on their face that out of the blue they press 1 and it turns into r t y Q. Particularly not with a configuration that's fresh from the Quick Setup Wizard, and having never configured anything to do with R T Y or Q. This problem doesn't exist for everyone else, just you. It takes expertise because we have to find out where your R T Y and Q are coming from.

The first thing that sticks out from this diagnostics is the 45 instances of the Agent process. Have you rebooted since this problem started?

If that doesn't help then I'll actually need the diagnostics from 32-bit WoW rather than 64-bit WoW though. There's an option to switch between 32 and 64-bit in the WoW launcher, or alternatively you can give me diagnostics from running it with Inner Space instead of without and it'll be the right version.



The issues you're describing that DONT sound like random keys coming from an unknown source, can probably be solved by going through the WoW Quicker Start Guide starting with http://isboxer.com/wiki/WoW:Quicker_Start_Guide#Part_3:_Make_sure_the_ISBoxer_Addon_is_not_disabled

Thank you for the help, but key switching aside what could be happning with one client not wanting to use mapped key's. When both the addon is on and the same key maps work with the other character on the same team, while playing at the same time. or why that same charcter dosnt fallow when I screen switch!? Thanks again xDDDD

[lax]

That's kind of vague but I'll try...

for your auto-follow question
* Characters will only auto-follow when you switch if you enabled that option during the Quick Setup Wizard (on the final page). If you have, then when you switch Characters, ISBoxer will send the keystroke for auto-following the character you switched to. Otherwise, press Alt+F to make them follow. If Alt+F doesn't work to make them follow, then we'd go back to the WoW Quicker Start Guide.
* If you manually added an extra Slot to a Character Set after using the Quick Setup Wizard, it's probably not set up ideally. The wizard configures parts of each Slot, like which CPU cores it should use, and what Mapped Key should be performed when you switch to the window (e.g. "Follow/JambaMaster" to make others follow).

As far as "one client not wanting to use mapped key's", it would help to know specifically what behavior you are seeing.

For example... "I press 1, and my main guy attacks, but on my second guy's screen it says I don't have a target, and he doesn't attack". This might suggest that the attack part (pressing 1) is working fine, but we need to fix the assist part (which requires the ISBoxer Addon, which will have a WoW Macro in it, and it will assign a key to in the game). That's typically easily fixed by either following the Quicker Start Guide (e.g. to turn on the Addon in the window that the macros don't work in) or this FAQ entry FAQ: I recently set a key binding in the game and now assist doesn't work

lolz Thanks again , had already tried all that xDD and it's fresh as you can tell from all the re-install's. Though I cant quit figure it out, I guess I just have to keep mexicaning it ,lol just like I did having to put intract with target on 1 instead of a chosen keymap becuse of the key switching bug ,lol and with this new keymaping deal I guess I'l just have to change my druids from resto and balance to dual balance ,lol at least until mop comes out hopefully an update or somthing will fix it later. xddd but ty ,lol