Is Caps Lock Dead?

An anonymous reader asks "Recently I have noticed that I haven't used caps lock other for any purpose other than hitting it by accident. Once upon a time, COBOL was written in all caps, and other languages like BASIC and Fortran were not case sensitive. Capitals were the way to go for writing code. Does the caps lock key serve any purpose any more, and if not, should it be removed, moved, or replaced?"

Comments

No! I use CapsLock as my "ESC" key

[ClarkEvans]

especially useful in VIM.

USN

[mysterious_mark]

Actually, in the US Navy and other branches of the service radio messages all always in all caps. These were a pretty routine part of life on ship (for Officers / admin personnel etc) We would compose the messages on a PC w/ word processor, print hard copy, then have approved by CoC. Radio men would send them out encrpyed, hard copies were always kept for paper trail. A ship my send dozens or even hundreds of these a week, so the're quite common. There are a few who may need cap locks who aren't programmers. M

Re:Yes

[falzer]

Here's how I made capslock an extra control in Windows 2000/XP.

Go to this path in the registry editor:
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Keyboard Layout

In that registry path, add a new binary value, like so:
Name: Scancode Map
Type: REG_BINARY
Data:
00 00 00 00 00 00 00 00
02 00 00 00 1D 00 3A 00
00 00 00 00

This required a reboot to take effect (for me, anyway).

Happy Hacking

[yet another coward]

Use the Happy Hacking keyboard. It has no Caps Lock. Its Control key is in the right place.

Re:Computer freeze check

[Cerv]

But Num Lock and and Scroll Lock make Caps Lock redundant if that's all you ever use it for.

Re:Yes

[JPriest]

Fixed link
Download is for "Windows Server 2003 Resource Kit"

Re:Replace it with a key labelled [help]

[runderwo]

Oh yeah... did I mention that it has a USB hub in it? Why the hell are we still shipping PCs with 12-year-old PS/2 technology?

Easy. Because USB is not a perfect replacement for PS/2 input devices.

• There is a large amount of latency on the USB bus as well as software latency incurred due to processing the USB packets. There is practically no wire latency with PS/2 and the protocol is dead simple to parse. You can create a little microcontroller project to interface almost any simple device to a PS/2 port. With USB, you need a separate ASIC to even begin to get anything done.
• USB controllers typically share interrupt levels with other PCI devices. On systems without an IO-APIC, this translates into increased software overhead on every interrupt, because the interrupt handler for every device sitting on that interrupt is invoked. Whereas with PS/2 devices, you have an IRQ reserved for the keyboard and an IRQ reserved for the mouse. Since they are edge triggered ISA interrupt lines, there is no possible way for them to be shared even if you wanted to. Therefore the correct interrupt handler (and ONLY the correct one) is invoked in response to a PS/2 event.

In short, there is no possible way on any but the fastest of current machines for a USB mouse to approximate the responsivity of a PS/2 port mouse being sampled at 200Hz (the maximum rate the port will tolerate).