Not so much a clueless luser thing or anything like that, but it's IT related, so I'll put it here.
User calls me up yesterday because his computer monitor abruptly went into "power save" mode, as it does when there's no input going to the monitor, such as when it's been idling for a while or if the computer itself is turned off.
Only, the user had been typing away in a report he was writing for quite some time prior to it shutting down. And it wasn't responding to any more input. Keyboard, mouse, neither worked.
SOP at The Client is if this happens, reboot the machine. Do NOT meddle with the cables and connectors in the back of the machine, because the average user is not really IT savvy enough to know what they're doing. (i.e.-- leave it for the professionals to do
As it happens, the user had recently been transitioned over to "ENVY," a new desktop environment that The Client is using. (NOTE-- this is just what I'm calling it for the purposes of obfuscation.)
After I told him he's gonna have to reboot his machine, he gave a sad little laugh and said, "I thought the ENVY environment was going to be more stable."
I replied, "Well, yes, but we're still using the same old hardware, so..." which got another sad little laugh from him. He said he'd reboot and call back if the issue persisted.
All this comes down to the usual IT mantra-- "Crashes happen. Save often."
User calls me up yesterday because his computer monitor abruptly went into "power save" mode, as it does when there's no input going to the monitor, such as when it's been idling for a while or if the computer itself is turned off.
Only, the user had been typing away in a report he was writing for quite some time prior to it shutting down. And it wasn't responding to any more input. Keyboard, mouse, neither worked.
SOP at The Client is if this happens, reboot the machine. Do NOT meddle with the cables and connectors in the back of the machine, because the average user is not really IT savvy enough to know what they're doing. (i.e.-- leave it for the professionals to do
As it happens, the user had recently been transitioned over to "ENVY," a new desktop environment that The Client is using. (NOTE-- this is just what I'm calling it for the purposes of obfuscation.)
After I told him he's gonna have to reboot his machine, he gave a sad little laugh and said, "I thought the ENVY environment was going to be more stable."
I replied, "Well, yes, but we're still using the same old hardware, so..." which got another sad little laugh from him. He said he'd reboot and call back if the issue persisted.
All this comes down to the usual IT mantra-- "Crashes happen. Save often."
Comment