Windows 8 - Auto run key not working

[Casey II]

You have to mash the key a dozen times for the auto run function to work in Everquest.

Tried three different keyboards.

Blacks will pay for this.

[Faerie]

Autorun using forward and the enter key.

[Casey II]

That's neat. Thanks

Anyhow, I rebound the function to a key other than numlock and it works just fine.

This is not ideal however, as I've grown accustomed to numlock being my auto run key for over a decade. I've decided not to install windows 8 on my main machine. I guess.

[Faerie]

Yeah :)

It's actually more useful than numlock because you can autorun in any direction, but I prefer numlock too.

[myriverse]

Hmm... my Win8 didn't have this problem.

But I ended up changing from numlock anyway, because I hate it.

[skeletoria]

I will never upgrade to Win8..Vista was bad enough..but I never thought once about running games on it.
Win98/Xp FTW

[August]

This is more than likely because you either have a bad serial connector (or USB connector) or you have numlock mapped to a special function in another program.

For keyboard input, you are actually using a HID driver (human interface device). Every time you press and depress a key there is a HID report being sent to the kernel that processes I/O. In most cases, this would be a report that contains what key, and what it did. In that aspect, pressing 'Num lock' is no different than any other letter or combination thereof.

This could be caused by software you have installed alongside EQ. More than likely, something is intercepting this report - as it's not making it to the EQ Client.

What kind of keyboard(s) did you use? Are they programmable? Did you have specific drivers downloaded for your keyboard?

[Casey II]

I tested it with a Logitech G19, Logitech G15, Razer Arctosa, and a shitty Wal-Mart keyboard. Driver software was installed for the Logitech devices but I could never get them to establish a connection with the Logitech keyboard software, the other two just use windows default drivers.

[Mithas]

I use Win8 and NumLock works for me.

[August]

What is funny is that people hate on Win8 so much and really have no reason to. People don't realize that all Windows releases rest of the shoulders of their predecessors - its not like the kernel is re-written every release. It's not like the HID driver went under drastic changes.

To the normal user, the only thing they see in a new Windows is the update to the SHELL - believe it or not, this is only 1 large team in Windows - there are a myriad of other teams that handle all types of things like security, device compatibility, driver stacks, driver hosts (UMDF/KMDF), development experience, etc.

Windows 8 is literally Windows 7 with a different shell (modern UI - the tiles) and tons of updated components that increase performance, lower power consumption, and a whole bunch of bug fixes that you probably weren't even aware of. The Windows 8-hate bandwagon is solely based on the new modern context UI - everything you loved about Windows 7 is actually still there - protip: right click on where the start button used to be - you will see a very familiar menu.

-Tomtee

[kingsBlend]

http://www.gfi.com/blog/wp-content/uploads/2012/06/linux.png + http://www.winehq.org/images/winehq_logo_glass.png

[Hollywood]

That's neat. Thanks

Anyhow, I rebound the function to a key other than numlock and it works just fine.

This is not ideal however, as I've grown accustomed to numlock being my auto run key for over a decade. I've decided not to install windows 8 on my main machine. I guess.

Autohotkey
http://www.autohotkey.com/

Make a new script and tell your desired key to emulate your destination function key.
i.e. numlock :: insert (assuming you've bound auto run to Insert)