• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join freeLog in
    Want zero display ads or expanded classifieds tools? Compare plans.

Get off my LAWN! "Grumpy Old Farts"

Status
Not open for further replies.
I am familiar with the Microsoft "process". Scratch familiar - experienced. lol.

A good portion of my IT career was client support, too. I just said something like "It's never done that before" or "What were you doing right before that?". lol.

I bought a new Surface Go 2 back in Dec. Was working fine until the 20H2 update in Jan. The camera and mic stopped working. I've done all of the recommended fixes several times, reported the problem to MS and the community forum - No response. Tons of other people with the exact same problem on different computers. Some with built in devices, some external. I did find an article that said MS knows about it but no other info. I'm confident it's something in 20H2. Our laptop's built in camera and mic still work since 20H2 has not been installed (and will not be).

I never want to be the first kid on the block or, for that matter, a beta tester. Even being retired, I have better things to do with my time, just sayin'.
 
Microsoft's idea of beta testing used to be to shrink-wrap a few million copies and ship 'em out to the stores.

Which, oddly, makes them one of the white hats
(vs. the black hats like in cowboy movies)

The amount of computing power it would take me in 1973 to make such a catastrophic computing event today with a smrtphn is incomprehensible.
 
IT Professional example. You might have to click the "pop out" at the upper right or call the help desk.

[This invalid link has been removed]

I'd like to give proper credit for the video but someone sent this to me back in '07 and I couldn't find it on youtube.

This is spectacularly unfunny funny
 
I bought 18 new Dell Latitude 3310 two-in-one touchscreen laptops early spring. Along with their WD19TB docks. Getting ready to set up three laptops I got a white BIOS pre boot screen saying, "power adapter is insufficient for laptop. Attach power supply." After trying six docks the last tech rep told me it was an error either in the laptop or dock. The dock was misreporting the amount of power the laptop was receiving. So, we went through the month long process of talking to some replacement return techs and managed to return the most of them. Without admitting mistake, Dell released the "new" Dell dock WD19TBS and I received one for testing. The S means that in the BIOS you can uncheck the setting that says, "stop boot process if low power is detected and ask for permission, or, ignore message and continue on."

Mind you they didn't solve the power supply error, they just provided a switch in the BIOS to ignore the message on boot up. Now the laptops boot but they have a large yellow exclamation point over the battery icon when hovered over says, "battery may take too long to charge. Try different power supply." :banghead: We ordered 18 new adapters with the S icon and Dell has promised to eliminate the misreported power issue. After all, the laptops use 45 watt power supplies and the docks are 130 watts! Go figure! :poop:

Wanna hear the fun part? I was supposed to have the 18 laptops deployed by the end of June. The power supplies won't arrive to Dell until mid-July.
 
Last edited:
IT Professional example. You might have to click the "pop out" at the upper right or call the help desk.

[This invalid link has been removed]

I'd like to give proper credit for the video but someone sent this to me back in '07 and I couldn't find it on youtube.

That is so unbelievable that it is believable...;).
 
Adventures in Tech Support Land: Part of my first IT job was on a 24/7 tech support hotline. We supported users worldwide so you could get calls at any time that could be in several different languages. That made for some interesting conversations trying to diagnose a technical problem with a remote user who didn't speak much or any English. The Korean calls were the most "fun".

Back in the days of dumb terminals on a timeshared network (what used to be Tymshare for you old IT GOFs) and 2400 baud communications, a user called to say his screen was moving very slow. A screen moving very slowly with a max baud rate of 2400 is VERY SLOW. I told him to shut down and make sure that his cables were not kinked up so the data could move freely and call me back. After he unkinked his cables he called back fat dumb and happy that I had fixed his problem.

One Sunday afternoon a woman working at the Pentagon called the hotline crying that she couldn't print a report for a colonel (Klink perhaps?) who needed it immediately. After a couple hours and many calls back and forth trying this that and the other thing with no success she sobbed that the printer hadn't worked properly since it was moved to a new location. Me: "Is it plugged in to the wall socket?". Her, after checking: "No".

After our company was awarded the contract for another multiyear term, the GOV had a contractor from another company call the hotline every hour for 24 hours to check that we were indeed providing 24 hour support. He did and we did.

At one time there was evidence that a user in Germany had their account hacked. I played a small part in the investigation by compiling usage statistics and some other info. It turns out the account was hacked and the culprit was eventually found out. There was a PBS documentary about this incident (mid to late 80's-ish). Some of the folks I worked with and for made it on screen. I remained an unsung background player.

Another user used to call every time they needed to produce a periodic report seeking help on how to generate the report. Your tax dollars at work.
 
Status
Not open for further replies.