Hi!
I'm using AHK now since 2 years for remapping my keys on my old thrustmaster tacticalboard (a gaming keyboard like logitechs g-13) cause there are no win7/vista drivers/software available for this old device.
since yesterday punkbuster kicks me from all battlefield 3 servers for using an not allowed program ...
"Game disconnected: you were kicked by PunkBuster. Stated reason: PunkBuster kicked player 'DecayNeXuS' (for 0 minutes) ... RESTRICTION: Disallowed Program/Driver 89262"
evenbalance support ticket answer ...
"This kick is usually caused by one of the following programs running. Disabling them should stop the kick.
Auto Hot Key
Blockify
Unblock-us
Memory Cleaner
Ad Munch
Black Glass Enhanced
If you do not have any of these programs running, open this ticket back up and state what you do have running, especially anything that might be similar to the above."
i've played a few rounds without ahk and it seems to work.
is there a workaround to get ahk still running with punkbuster games?
why they kick ahk users?
alternative program for remapping keys?
can't use my tacticalboard without remapping the keys cause the default layout is useless
Punkbuster Kick for using AHK
Started by
NeXuS
, Jul 19 2012 02:36 PM
4 replies to this topic
#1
NeXuS
Posted 19 July 2012 - 02:36 PM
#2
Posted 19 July 2012 - 05:17 PM
I've read from several posts that compiling the script to an exe file and then running it sometimes helps, as opposed to just running the .ahk script.
#3
Posted 19 July 2012 - 05:26 PM
http://en.wikipedia....wiki/PunkBuster See the sections labelled "Published Features" and "EULA Details".
This looks like a seriously invasive program. It's not likely they will permit AutoHotkey to run but, since they have already popped you for it, you could try compiling your script with a diff exe name and changing autohotkey's icon in the process list. If they're doing a full memory scan for signatures though simply compiling the script may not work. What I find particularly offensive is the section in the EULA about the hard drive scans. They really have no business mucking about in my drives, or anyone's for that matter.
This looks like a seriously invasive program. It's not likely they will permit AutoHotkey to run but, since they have already popped you for it, you could try compiling your script with a diff exe name and changing autohotkey's icon in the process list. If they're doing a full memory scan for signatures though simply compiling the script may not work. What I find particularly offensive is the section in the EULA about the hard drive scans. They really have no business mucking about in my drives, or anyone's for that matter.
#4
NeXuS
Posted 19 July 2012 - 06:05 PM
[quote name="TheDewd"]I've read from several posts that compiling the script to an exe file and then running it sometimes helps, as opposed to just running the .ahk script.[/quote]
still using a compiled exe but also checked just running .ahk script ... same problem
quote="girlgamer"] It's not likely they will permit AutoHotkey to run but, since they have already popped you for it, you could try compiling your script with a diff exe name and changing autohotkey's icon in the process list. [/quote] ... i will check that
still using a compiled exe but also checked just running .ahk script ... same problem
quote="girlgamer"] It's not likely they will permit AutoHotkey to run but, since they have already popped you for it, you could try compiling your script with a diff exe name and changing autohotkey's icon in the process list. [/quote] ... i will check that
#5
Posted 03 January 2013 - 02:04 AM
does, changing the signature, or modifying using reshacker, or running it internally in a another wrapper program?, or using the dll version of autohotkey_h???




