Login with username and password (forgot your password?)

Thanks! And I'll check with my KVM vendor.
Cheers!
Bil

Thanks for that, lanux128 -- sadly it doesn't seem to maike any difference. I tried ending the ipoint.exe process, and saw no difference in keyboard behavior in general, but also no change in the behavior of the CapsLock key.

I find it very strange that the ScrollLock key works perfectly normally on mouse down, but the CapsLock key only registers on the mouse up action.

Anything else I can try? Is it possible the issue isn't with my keyboard but with my KVM switch? (Kind of far-fetched, but I'm grasping at straws.

Thanks - that would be very generous. I don't have Autohotkey .. but I'm growing unhappy with the macro program I've been using -- I think it's time to switch.
Bill

Thanks, but I'm a newbie to scripting. Is it enough to add this to the ahk script? Or do I need to recompile the executable. And if I need to recompile, how do I do that?

Thanks!
Bill

Sure! It's a Microsoft Wireless Laser Keyboard 7000. The software for it lists only two options for the CapsLock key: Disable it (not selected) and show the caps lock status on the screen (enabled). I disabled the display option with no improvement in the behavior of the key.

Any thoughts?

Recent problem - hope I can tweak the settings to fix it.  Running on a wireless keyboard through a KVM switch, the CapsLock key doesn't trigger until I release it -- the time doesn't start on mouse down, but on mouse up.

The Scroll Lock key is still working fine -- I can see the little millisecond display and the acknowledgment of key state change happening on mouse down action.

But for Caps Lock, I don't see the little millisecond display until the mouse up action occurs, and of course the timer never advances.

FWIW, one of the computers this happens on is a laptop. When that laptop is off the docking station and I'm using its own built-in keyboard, the Caps Lock timer works just fine. The problem only happens with the new wireless keyboard.

Amy suggestions?

Thanks,
Bill

I'm running two desktop PCs and two laptops through a KVM switch, sharing a single wireless keyboard & mouse and monitor.

My main computer is a laptop, and CapsShift & ShiftOff work fine on the laptop's keyboard. But on that same laptop using the wireless keyboard running through the KVM switch, they don't. I can see CapShift being run, (the on-screen dialog opens momentarily) but it doesn't trigger on the CapsLock Down action -- instead it triggers on the CapsLock Up action. That means the 500 ms timer never reaches 500 ms.

Is there a solution for this?

Brilliant!!

Thank you.
Bill

That's cool. I didn't know the source script was available -- I don't think it came with the app downloads.

Boy, that seems to do the trick! Thanks for the suggestion!

Now if these two programs could be combined so as to reduce the number of things running in my SysTray, I'd be beside myself.

Bill

I thought Capshift was the answer to my dream -- I'd gotten to the point where I was considering gluing a thumbtack to my dreaded CapsLock key.

But it turns out, I have a behavior that foils CAPshift. When intending to use the left Shift key, I often strike both the Shift and the CapsLock key together. When I do that, the 0.5 second delay doesn't apply.

I would LOVE it if CAPshift could be modified to do exactly the same thing with the Shift-CapsLock key combination. Or even better -- to treat the Shift-Capslock key combination as equivalent to just a Left Shift key press.

Any chance for that?  Thanks for listening either way.

Bill