Keyboard - Hardware

[bobbysmith]

Yesterday everything was working fine.  Today when I turn on my computer, my G keys aren't emulating the proper keystrokes in my application.  I do all the normal stuff, checking profiles, etc.  The problem is, if I bind it to a 'normal' key like W or S, the application responds, so it can't be the profiler.  So I test it with the "Test Profile" option within the keyboard profiler, which should eliminate any profile-application problems anyway.

G1 bound to W

  W down, G1 down, G1 up, W up just as expected

G1 bound to F1

  F1 down, G1 down, G1 up, F1 up, also no problems

G1 bound to Ctrl

  Ctrl down, G1 down, G1 up, Ctrl up, but combining any of these breaks it

G1 bound to Ctrl + F1

  G1 down, G1 up.  Period.  This behavior is the same regardless of which Ctrl, Shift, Alt key I apply (right/left), and also remains consistent across keys other than function keys, such as numbers.  Binding to different G keys produces the same effect.

I have uninstalled and reinstalled, including wiping out all Windows keyboard devices and starting from scratch.  As I was typing this, it started doing something new.  The keyboard profiler app is crashing without giving errors other than Windows informing me.  Another strange symptom: when I hit a G key the MR key starts flashing on its own.  Pressing it does nothing.

I hope a combination of these odd behaviors can lead you to the cause of my problem.  Thanks in advance.

Windows Vista 64 (yes, I'm using the right drivers).

G15 version 1.

[CharlesB]

Sounds like a permissions issue, specifically in an application that's running as Administrator. The keyboard issues single keystrokes as hardware emulation signals, but combo keystrokes are executed like macros. What application are you attempting to use these macros in, and is it running as administrator? Can you temporarily disable UAC and see if that resolves the issue?

[bobbysmith]

I have tried running the app in question without admin priveleges, as well as running LGDCore.exe as admin, as I saw this in an earlier post.  If this were a permissions issue, why would the Keyboard Profiler itself not be showing the proper keystrokes in the test mode?