Press any key

[johnpost]

@Doug_K

Also except that the message appeared all too often in the days when keyboards were not hot swappable. I’ve known a few people who fried their PS/2 ports by plugging or unplugging a keyboard without powering down first.

@Musicat

I have built over 400 computers (PCs) and never saw one that caused anything bad to happen if a keyboard was plugged in or unplugged while the computer was powered.

In fact, I keep a PS2 kbd handy when my main unit, which has all peripherals USB-connected, needs to “press F1”, since the BIOS doesn’t recognize ANY USB devices until late in the boot sequence. If I get that message, I just plug in the PS2 kbd, press a key, then remove it. Works every time.

@Doug_K

I’ve seen it happen several times. It was always one of those things where, sure chances are nothing will happen, but if it does, the results are expensive. The manuals that came with PCs in the '90s always warned the user to power down before unplugging or plugging in anything. When USB first came out it was considered a huge breakthrough because it was hot swappable.

damage to a computer is an all depends on plugging in PS2 keyboard or mouse. i’ve seen it happen though i’ve seen it not happen more. a USB could be used with a damaged PS2 port if needed.

and USB keyboards and mice don’t activate early. in a dual boot machine i have the GRUB doesn’t respond to USB and need a PS2 which i just leave connected..

[ftg]

If you plug in a PS/2 or AT keyboard connector right, nothing bad should happen. But it’s easy to have it aimed a little wrong and short out a tiny surfce mount fuse on the MB. (ATs especially, but I’ve seen it on PS/2 boards.)

I fixed these MBs back in the day by desoldering the fuse and replacing it with one from a deader MB.

You have to be a bit more aggressive to do damage to USB port this way. But they go bad with surprising frequency due to faults in cables and whatnot. Hence the advice to try another USB port.

[pulykamell]

@Hail_Ants

You don’t see this too much with a GUI (i.e. on a Mac or Windows) anymore, but it was a standard ‘pause’ method back in the days of text-only terminals & programs.

Anybody who learned BASIC will remember:

50 IF INKEY$="" THEN 50

INKEY$ was a variable that equaled whatever key was being pressed, so as long as it equaled a null string (i.e. “”) the program looped until it equaled any character (IOW when you pressed any key).

Well, to be pedantic, on a number of computers in a simple BASIC program, it couldn’t just be any old key. For example, on a C64, pressing the Commodore key, the shift, the caps lock, or control (and perhaps restore and, well, run-stop for obvious reasons) would still equal a null string unless it was pressed in combination with another key.

[drewtwo99]

does pressing the SysRq key do anything at that prompt?

[cochrane]

Hit any key to continue.

[Chronos]

Or then there’s “Press any key to continue, or any other key to quit”.

Yes, I did actually use that one once.

[Cartoonacy]

@Darth_Panda

You should have to type a-n-y-k-e-y for it to continue

I remember reading a webcomic several years ago where a nearsighted user got the message “Press any key.”

He hunched down over his keyboard and pressed “A.”

The message on the screen changed to “Do you want to save your work (Y/N)?”

Still looking down, he pressed “N.”

The screen said “Are you sure (Y/N)?”

Still looking down, he pressed “Y.”

He looked up. His eyes got **real **big.

In the final panel, a tech sitting at the help desk hears the phone ring and thinks, “Why did I just feel a chill run down my spine?”

[beowulff]

@cochrane

Hit any key to continue.

That’s a Mac II!

[Sunspace]

@beowulff

That’s a Mac II!

I was thinking the same thing. And isn’t that one of the ducks from Professor E. McSquared’s Intergalactic Calculus Primer?

[Doug_K]

@Hail_Ants

You don’t see this too much with a GUI (i.e. on a Mac or Windows) anymore, but it was a standard ‘pause’ method back in the days of text-only terminals & programs.

Anybody who learned BASIC will remember:

50 IF INKEY$="" THEN 50

INKEY$ was a variable that equaled whatever key was being pressed, so as long as it equaled a null string (i.e. “”) the program looped until it equaled any character (IOW when you pressed any key).

@pulykamell

Well, to be pedantic, on a number of computers in a simple BASIC program, it couldn’t just be any old key. For example, on a C64, pressing the Commodore key, the shift, the caps lock, or control (and perhaps restore and, well, run-stop for obvious reasons) would still equal a null string unless it was pressed in combination with another key.

To be even more pedantic, on the C64 you would use the GET command, as in

50 GET B$ : IF B$ = "" THEN 50

and that didn’t actually wait for a keypress, it pulled the next available character from the keyboard buffer, which could already have keystrokes waiting to be read. It was common practice to clear the keyboard buffer first, with

40 GET B$ : IF B$<>"" THEN 40

just in case the user had “typed ahead”, to make sure the program would really pause.

[pulykamell]

@Doug_K

To be even more pedantic, on the C64 you would use the GET command, as in

50 GET B$ : IF B$ = "" THEN 50

and that didn’t actually wait for a keypress, it pulled the next available character from the keyboard buffer, which could already have keystrokes waiting to be read. It was common practice to clear the keyboard buffer first, with

40 GET B$ : IF B$<>"" THEN 40

just in case the user had “typed ahead”, to make sure the program would really pause.

Or POKE 198,0 also clears the buffer.

ETA: Which reminds me. You can also do POKE 198,0 : WAIT 198,1 to clear the buffer and wait for a keypress. Basically, they correspond to line 40 and 50 quoted.

[Shoeless]

@cochrane

Hit any key to continue.

A project I worked on several years ago had user documentation that was commonly referred to as “The Duck Book”, because the developer who wrote the documentation had that picture on the cover with the caption “Before you do this, READ THIS!”