They are out to get me. ALL of them.
So here's the wonderful fun story of what went down today. :DI was working. I got to my register (after hunting for one) and I was scanning a computer case. It was on the cart so I swung it around the counter partly to scan it. I pull on the cord, and it has a coil style wire so it can stretch.I pull. I didn't realize there was a tangle keeping it from pulling. I yanked the computer off the cubby hold (it's a small case.. like about 2 big textbooks stacked together, maybe a tad thinner, but a bit wider/taller). It crashes to the floor. My screen goes black, lights turn off on the computer. Set it up, check connections - nothing. Reconnected everything - nothing. Another CSR checks it - nothing. Two managers check it - nope.I killed the computerSo throughout that day, the other registers I was at either failed to print receipts, or freeze up during transactions. :(
As someone who works in IT, this is what happens when you call someone about that computer.
Your Manager: "Hello, my register computer isn't scanning anything"IT: "Does it give an error message?""No, it doesn't do anything""Is everything plugged in?""Yes""Is there a power light on the front of the computer?""Yes""Can you see the screen""Yeah, I'm touching the screen right now""…Okay then…Uhh, what version of the software are you running?""I don't know""I'll explain how to check, and then you let me know""Alright""Okay, so open the software, and click on the "help" button at the top, do you see that?""Okay""Now go down and click "about"""Okay""Now there should be a little section in the corner that says the version number - it will probably say 3.1""Hmmm, give me a minute""Alright.""…Hmm, I cannot click on help""I thought you already clicked on help?""No not yet""Why did you say "okay" and let me continue on with the instructions?""I didn't know I was supposed to do that, I thought you were doing that for me""…Okay then…I'll connect to your system and do that for you. On the front of the computer there should be a little label with the computer name on it, I'll connect to it over the lan with radmin or something""Yes""…What does it say on the label?""It has the company logo, and below it some code letters""…Can you read the code letters to me?""Yes, it is 420-D-00123""D? D stands for a desktop computer, that should be an R for register.""Oh yes, I'm sorry, I meant R""…Okay then…Let me try and connec-""Do you see the computer yet?""Just give it a minute here…Alright, it's saying that it can't find that computer name, can you read it again?""420-R-00123""Hmm, still can't connect. Can you look at the back of the computer, there should be an ethernet cable - it looks like a thick phone wire - just make sure it's plugged in.""It's plugged in""Is there a green or orange light flashing beside it?""No, I see no light""Hmm, alright. Maybe it's just disabled on the computer, can you go to your desktop and right-click on the My Network Places icon?""Okay""Now go to properties""Yes""Now it should list your connections. One of them should be called Local Area Connection""Okay""You see that one?""See what?""…Are you following along with what I'm saying? Did you go to properites on your computer?""I cannot, the screen is black""It's black? Like it completely shut off?""Yes it hsa been shut off for a while?""Oh, well that's why I can't connect, why did you turn it off?""I did not turn it off, it was my employee""Oh…Okay…Let him know you're working with IT to try get it fixed, and not to touch it. Can you turn on the PC for me please?""No, it will not turn on?""Oh? DId anything get unplugged at the back when you checked the internet cable?""No""Hmm, at what point during our conversation was the computer shut down? I can check the logs of the server connections and see if there was a conflict or something that crashed your particular system.""My employee knocked it down before I called you?""Well that could also cause it to not work I guess, if it got damaged it could keep shutting off.""I don't know, maybe. It hasn't turned on since it fell.""I thought you said it fell before you called me?""Yes""But when I asked if the power light was on, you said yes""Yes, I have power everywhere. The lights, the air conditioning - we have power everywhere""…You told me you could see the screen""Yes, I have the screen right in front of me, and like I told you, it is black""…Were you physically touching the screen with your hand?""Well yes, I wouldn't head butt it or anything""So basically you cannot scan, because the computer fell, and now it won't turn on""Yes! I cannot scan!"First rule of IT support - the customer always lies. Second rule, they are fucking stupid. Third rule, you do not point out that the customer is a stupid lying fuck who can easily waste 45 minutes of your time.Actually, my manager (they are the ones to call IT) did that. However given that it's a computer store, and most of the managers are trained to actually understand the system (mostly) or to understand most of the problems, this unusal one went like….. BTW IT's questions are my own guess.
"We need to kill the signal to PO 5 for ID… aloprimo" (in order to log out when a system is down, IT manually ends the login/signal).IT: "Okay… what happened""The system cra… It broke. it's not turning on"IT: "And what caused it? Did you check the connections?:"He went to scan an item, and yanked the computer out of the area, making it fall and crash to the ground"… My manager laughs afterwards and then I feel stupid and promptly bury my head for a moment or two. :/I always love reading those conversations.
@Firestormx: That sounds about right lol.
And with my gf being with me, I tought her a bunch about computers just being around me that she pretty much fixes everyone's stupid problems at her work.