If he had room for a few banks of reel-to-reel tape machines and a punched-paper-tape output device, they’d be in there too.
The version I knew was
In other words, notice to visitors, you can look but don’t touch.
I am amused that someone would think a machine wprth millions would have blinking lights just for show.
-
“Hey, the customer is paying millions for this machine and expects something more than a boring big metal rack. Let’s put some blinking lights! The customer will like that!”.
-
But this computer is for the Pentagon to calculate nuclear explosions.
-
So much the better. The military just love blinking lights. They will choose our IBM over Univac mainly because it has more blinkinglights, and in two colors! No contest!.
No, I’m not wrong.
I was specifically talking about the photo referenced in the quoted post.
The photo is of a (relatively) modern computer - a Connection Machine from the '90s. The lights on it are for decoration. As I said in my post, they could have been used for troubleshooting, but were unnecessary for the operation of the machine: http://blogs.discovermagazine.com/sciencenotfiction/tag/connection-machine/
Next time. please read the entire post before responding.
My favorite Hollywood computer was the one in Desk Set. Lotsa blinkenlights, and, if I am not mistaken, the tape drives had no tape & spun in opposite directions.
Yes, you were wrong. The lights indicated the state of the registers and were used in actual operation. Plenty of evidence has been shown of this. The photos show they were labeled with the different register names. It has already been explained what they were used for. The OP was asking a general question. The fact that you can find an instance where a modern computer has lights which are less used or useful does not change the general fact that the lights were used and necessary.
Old days aren’t so far away. On my networking shelf, I have a router, switch, print server, modem, and phone adapter, all with blinking lights. Very retro at night. Most of the time they mean nothing, just a hypnotic background visual, but if something went wrong (i.e., cable is down) or I have a question (connection speed of a device) they come in handy.
Now, if we can get to the origin of the machine that goes bing…
Maybe I need to make my posts simpler for you.
I’ll try to write in smaller words - when I wrote “Those” I specifically meant the lights on the Connection Machine in the photo.
I worked I on DG Nova, so I am well aware of what the indicator lights are for on old machines.
Yup. Here’s Data’s noggin: http://images1.wikia.nocookie.net/memoryalpha/en/images/7/78/Positronicbrain.jpg
Now, behold the M-5 multitronic computer: http://images2.wikia.nocookie.net/memoryalpha/en/images/3/3e/M-5.jpg
The suspiciously similar Atavachron: http://images4.wikia.nocookie.net/memoryalpha/en/images/0/03/Atavachron.jpg
Which looks a whole lot like Gary Seven’s Beta 5 computer: http://images1.wikia.nocookie.net/memoryalpha/en/images/4/4b/Beta5Computer.jpg
One might take this as proof that some computer company is going to be as dominant in Kirk’s time as Microsoft is in ours.
Another old-timer from the PDP-11 era. I did indeed use the lights to see how things were going. It was sometimes possible to tell if the* program was in an infinite loop or just taking a long time by looking at the lights. Then I’d stop the program and use a switch to step thru the loop to determine what it was doing.
I can still look at network gear and detect unusual activity by a quick glance at the lights.
*of course it was “the” program. These things only ran one program at a time.
I thought the turbo light was also for accuracy. I believe it dropped the speed down to 8MHz and some programs were written to compensate for the inaccuracy in calculations that the 8MHz processor made. Or, something like that. I remember in Pascal class in high school (circa 1992) we wrote a program that compensated for the 8MHz processor for large calculations.
Any ways, as far as blinky lights go, I dragged out this rack mount, modular, modem chassis from UMD many a year ago. It consisted of many 2400 baud modems that were in cards. When you turned it on it did this fantastic boot sequence where they all cycled up and the lights lit up and scrolled and the occasional random lights would flicker from time to time. We called the machine the BLM-14/2400.
Which stood for “Blinky Light Machine” and the 14/2400 was for the 14, 2400 baud modems. We had a friend fooled for months thinking it stood for balanced-line-monitor or whatever. We even made fake excel data for him as well. It was great.
eb
The lights on the Connection Machne did serve the purpose of diagnostics/performance tuning, but they also had a mode that would flash them randomly to look more interesting. When you have a multi-million dollar machine it is sometimes necessary to make it look cool to the folks that authorize the money to buy it.
Correction: “When you have a multi-million dollar machine it is [del]sometimes[/del] always necessary to make it look cool to the folks that authorize the money to buy it.”
Stranger
But does it go “ping!”?
You’re both right, so quitcher bitchen.
Yes, old computers had useful lights that were actually used by programmers (to read registers, etc.).
Yes, modern computers have useful lights that are actually used on occasion (connection lights, etc.) but that most people ignore most of the time.
However, a few years back I was at a small technical seminar given by the head of a giant, new, multi-gazillion-dollar lab that had been set up. Spiffy new lab had a glassed-in data center for their servers. Servers in the lab had all been turned around with the backs faced to the glass…so that the VIPs on tour would get to see blinky lights, because otherwise the deep pockets didn’t feel like they were getting their money’s worth.
I can’t find the links now, but you can buy panels of just blinky lights, purely for effect.
In fact, there’s a guy that sells blinky light & fake knob panels for music studios, for much the same reason. Some of the testimonials on his site are hilarious.
I develop hardware for embedded computer systems. Unlabeled blinkenlights are actually still very useful in this day and age. We have prototype boards for phones and they almost always have blinkenlights and various places in the software to run the phones the software will put out a specific pattern. This is basically like a print statement in a program running in the terminal. We can see what the software is doing. What the lights mean varies with what we are trying to debug. Usually we get past the blinkenlights stage pretty quickly and have useful messages sent over a USB link but for initial debug they are of great benefit.
If a CPU was inaccurate at a certain speed, it would never be run at that speed in any kind of factory-default setting. This is why overclockers* like early revisions of any new CPU design: The factory doesn’t know what the precise limits of the design are, so they’re overly-conservative and default to only shipping machines that will run the CPU at a relatively low speed that they’re willing to guarantee.
*(People who run CPUs at an unusually fast speed regardless of what the company is willing to guarantee. For fun, usually.)
The above doesn’t take into account things like the Pentium FDIV bug, which only occurred in one opcode, or the Pentium F00F bug or the Cyrix ‘coma’ bug, which were rather subtle design flaws relying on the vagaries of uninterruptable states and pipelining. All of those bugs would have happened at any speed before the silicon began to melt.
It’s possible to have bad RAM, though, which might only mainfest when you do RAM-intensive tasks. A number of early Linux enthusiasts were stymied by SIG11 errors from gcc when they tried to compile the kernel due to bad RAM their crappy BIOSes would pass without a complaint. I haven’t heard of anyone getting bitten by bad RAM in a long time, though. This, again, would likely not be speed-dependent, AFAIK.
Back in the good old days there were two “the blinking lights are no longer blinking” scenarios that would drive a spike of fear into my programming heart.
-
The lights were no longer blinking, but in a non-changing pattern with different lights shining at different intensities. That meant that my program was stuck in a loop (the lights were still technically blinking, but each light was going on and off in a steady pattern that caused human eyes to see it as shining steadily in a partially-lit state).
-
Each light was either solid on or solid off. “He’s dead, Jim.”
My late father used to proudly tell the story of how he compiled a program to play tic tac toe with the blinkenlights on the office machine. It became quite popular in the office. I miss Dad.
Thanks for all the responses so far. However, I don’t know if I am any closer to understanding how they convey information. I mean, I have a DSL modem and there are blinking lights on it, but those are LABELED and if one isn’t blinking, I know I don’t have a connection or something. And in some of the pictures you guys have posted it shows one row of lights and some look to be labeled somehow. However, if you look in this picture: File:Frostburg.jpg - Wikipedia
I mean, how do you just look and say, “Oh, the red light 36 rows down and in the 5th column isn’t blinking right, Frammer number 6 must not be working correctly.”
I mean, if there were linear rows of lights and the longer the row lit up, then maybe I could get some information out of it, but I mean, yeah, when you see a bunch of red lights and you say “Oh, the pattern’s not right,” how do you KNOW the pattern’s not right? And if it’s not working when the blinking lights are no longer blinking, couldn’t you just get away with one light then?
Thanks.
One of the machines I worked on displayed the binary value of the registers as well as the program counter (i.e., the address of the code currently being executed). If the machine halted because of an error you could see where in the code it was as well as the operands’ values. You could also often “single step” old computers instruction by instruction to see what was happening.