I was staring at my keyboard desperate for any distraction that would prevent me from doing actual work when I began to wonder: Why do I have a scroll lock key and is it still good for anything?
The answer to the first part of the question is probably “Because keyboards have always had a scroll lock key”, it probably goes back to some mainframe/dumb-terminal need. I’ll buy that, but why is it still there? Granted, it does make a pretty light go on and off when pressed. But I’ve never said to myself “Gee, I wish there was a way I could lock my scroll.”
You could probably reprogram it to do other neat stuff, but with the small amount of keyboard real estate, couldn’t we come up with a better key to take it’ place; maybe a “Death Ray” key, or a “Close that annoying pop-up ad window” key.
Using MS Excell, if you click on say cell E31 and use the up/down/left/right arrow keys with “scroll lock” off, the highlighted cell changes from E31 to E30, E29 etc.
With “scroll lock” on the whole screen/window scrolls up/down etc. while the highlighted cell stays the same.
Using “scroll lock” on you could for example have cell E31 selected, scroll to cell G100 to view the data and then enter data in E31. E31 will automatically appear when you begin to enter data.
Maybe not too useful. I use window/freeze panes or window/split myself.
As I recall, Scroll Lock was useful in DOS because it could stop the screen from scrolling when displaying large amounts of information so you could actually read it. These days, there are probably still people who use DOS, as well as using UNIX, Linux and other text command line based operating systems. Scroll lock my still serve a function for those who aren’t using graphical OS’s with a scroll bar on the side.
No idea about Sys Rq though. Mine has it as well and pressing it doesn’t do anything noticable. With my luck, it stands for “delete a random file off the hard drive”.
SysRq stands for system request. It is just part of keyboard becuase standards require that the Ascii code there still is accessable. It will actually do various system interrupts on Linux, but I never heard of anything that a MS system will respond to involving the key.
All th old keys are just for mainframe use, emulating ancient dumb terminals that the corporate world is still stuck to.
I still see lots of bureaucracies, like banks and insurance agents that have slick personal computers tied to Cobol programs with all upper case and “line editors” without wordwrap!
Some companies have systems so old and outdated that they require special keyboards with keys no one else has ever heard of.
Airlines spring to mind. I mean, how complicated is the database they use to track reservations? I ask if there are any aisle seats available… clickity - clackaty… What’s with all the typing?
I think I could whip up a reservation system in MS Access in about 3 hours… and I’m not very good with Access!
I actually did notice a difference in the MS-DOS editor depending on whether I had Scroll Lock pressed. Nothing besides that, though.
BTW, speaking of unused keys; I have an old 486 in the room next to me that has a MACRO key! I have no idea what it does/did, but no program I know has ever used it, and I made a program that printed the scancode of the key pressed, and it didn’t even detect it. Me and my friends are still convinced that it’s really a “set off an atomic bomb in a random city” key.
I think a macro key is just there so that you can program it to be used in place of a set of keystrokes. For example, you could (and I have no idea how) program it to be CTRL-ALT-DELETE, so that you don’t have to hit all those keys.
As others mentioned, the “SysRq” key stands for “System Request”, and dates back to the 3270 class of terminals used for connecting to IBM mainframes. If I remember correctly, on an actual 3270 terminal you pressed the System Request key to get the mainframe’s attention, which then allowed you to type in your next request.
Many of the original IBM PCs were also used as 3270 terminals to access a mainframe–I believe there was even an “IBM PC3270” model which was an IBM PC with built-in 3270 terminal emulation. IBM also sold a 3270 emulator for its standard PCs. So it was helpful to have a SysRq key handy on the PC keyboard.
However, I remember using another 3270 emulator package, from an IBM competitor, which went out of its way to be different, so you pressed something like alt-F3 for System Request for that package, and the SysRq key didn’t do anything.
Yep! In early 1998 I worked on a machine doing data input. Horrid ancient clunky old thing, proprietary or long-forgotten OS, 4 MHz processor, and a keyboard with a Clear Screen key and an Insert Line key (among others that were strange, but I had to USE those two). I’d hit Tab and about a second and a half later, the cursor would move to the next row to the right. Type some text, a couple seconds later it would appear on screen. You could not backspace or reverse-tab if you made errors: mess up and you have to DELETE THE LINE and start over. Find out you messed up 14 lines earlier and…yep! Nuke all 14 and start over. Folks in the office would hear me WHOPPING the keys and wonder what the hell I was doing, but to get any speed on the project you had to make SURE each key you hit was pressed completely, given the price of having one not register.
For those who don’t know what “print screen” does (it’s not readily apparent), in Windoze, at least, it takes a screenshot of the screen and places it in the clipboard, where you can then paste it into your favorite graphics program. I believe that in DOS it tried to send the text on-screen to a printer, but I’ve never tried it there.
Yeah, but it would crash about 8 million times. SQL Server is difficult enough to run on two servers at once, let alone the couple hundred you’d need for an airline (and that’s before you even start thinking about overseas clients).
Also, that clickety-clack noise you hear…surely if you used Access you’d still have to, uh, use the keyboard.
Very useful; I use it for all kinds of stuff - probably most often for extracting graphical info from data manipulation software to include in presentations. An old trick for those (I don’t count myself amongst’em - I consider fucking with somebody’s machine a capital offense) so inclined was to take a screen shot of somebody’s desktop and set it as their wallpaper and then hide all their shortcut icons - the result is their machine looks normal, but no icons appear to function - bad, very, very bad.
In DOS a print screen would send output to the printer, but if it was not enough (55-56 lines) to fill a page you would need to use form feed to get it out of the printer.
Jophiel mentioned Scroll Lock being used to stop the screen from scrolling when a DOS command’s output was running tons of text past you; that sounds reasonable, but I seem to remember using the Break key for that(?).
Yup, I remember printing from DOS. I remember if you needed a form feed, the command was Ctrl-l.
Another little trick with the Print Screen button: in Windows, Alt-Print Screen sends just the active window to the cut & paste buffer. Comes in handy when composing help manuals with screen examples.
As far as I remember, beatle, the only way to stop scrolling text was by quickly slamming Break. Just tested it all out on DOS 6.22 and 7.x.
I have older DOSes laying around, maybe one day I’ll try it out on 'em and let y’all know.
Oh and another use for Scroll Lock: I wrote this little program. I’d run it and all people would see is a black screen. They’d be like “wtf?” until their eyes finally went down to the keyboard where I had all three lights (NumLock, CapsLock, and ScrollLock) flashing in different patterns.
btw- Anybody know how PrintScreen and SysRq got jammed onto the same key?
)