![This is a question](/images/board_posticon.gif)
Our IT support guy has been in the job since 1979, and never misses an opportunity to pick up a mouse and say "Hello computer" into it, Star Trek-style. Tell us your tales from the IT support cupboard, either from within or without.
( , Thu 24 Sep 2009, 12:45)
« Go Back
![This is a QotW answer](/images/board_posticon.gif)
if it doesn't work - just switch it off and back on again - usually worded as "Power it down and back up again" by the more pretentious
( , Thu 24 Sep 2009, 17:55, 5 replies)
![This is a QotW comment](/images/board_posticon.gif)
Step one in troubleshooting most complex processes is to start the process again.
( , Thu 24 Sep 2009, 18:04, closed)
![This is a QotW comment](/images/board_posticon.gif)
Of course, it's the standard answer because 90% of the time it solves the problem!
( , Thu 24 Sep 2009, 20:16, closed)
![This is a QotW comment](/images/board_posticon.gif)
"Turn the computer off and leave it off for about 30 seconds. This allows accumulated charges in the condensers/daughterboards/flux capacitors to dissipate and allows the ram to slow down from being dynamic to static"
Gives them the illusion of it being some sort of actual technical step rather than IT fobbing them off.
( , Sun 27 Sep 2009, 0:12, closed)
« Go Back