Skip Navigation
145 comments
  • Needed to get a server back online when it's CPU cooler had failed

    Found some random cooler for a totally different CPU, smeared thermal paste on it and zip-tied the cooler to the mobo and case as best I could.

    That thing ran like a champ for almost 6 months till I got around to replacing it

  • Opened and revived a DOA GameGear by cleaning off the furry, green, PCB corrosion. Didn't have any Isopropyl around, so I used vodka.

  • Originally posted here, quoted below for convenience:

    Real story.

    I was in my late teens. My parents were dragging me to a tiny, kinda culty church every fuckin' weekend. Didn't really have much choice. (Hell, I hadn't even told anyone yet that I thought Christianity was 100% bullshit.)

    I had a reputation for knowing my stuff about computers. (Because normies -- particularly boomer normies like Pastor Dipshit -- don't know the difference between programmers and PC support.)

    So, one Sunday after the service, Pastor Dipshit asks me to look at his computer. His Outlook was giving an error dialog. Something about not being able to find an email on disk. Clicking the "ok" button just resulted immediately in another dialog, and while the error dialog was present you couldn't interact with the main window, so this rendered Outlook unusable.

    Turns out he'd gone and deleted a bunch of files from the filesystem. Like by navigating from "My Computer" down to the directory where Outlook stored its files. Rather than deleting emails through the Outlook GUI the way one is meant to.

    So, I mused "hmm, I wonder if it's just giving one error message per email that was affected." I could see in the window behind the error dialog that the total count of emails in his inbox was only a couple hundred or something.

    So I commenced to clicking as rapidly as I could. Probably about a minute of clicking later, no more error dialogs and Outlook was usable again.

    And everyone marveled at my "genius."

    I wouldn't be surprised if he didn't learn his lesson and continued to delete random files from the filesystem, but he kindof lost what was left of his connection to consensus reality and scared even my culty family away and we quit attending that church not terribly long after that, so I couldn't say for sure.

  • Early in my career (a long time ago), I was tasked with ordering replacement chargers for some laptops. I ordered several off Amazon and even though they were labeled as being what we wanted, they were apparently bootleg and were not, in fact, the correct charger. Fried a few laptops before I realized Amazon wasn’t the “Amazon” of yore selling first-party parts and I was ordering from random third party sellers. (That was all relatively new at the time. Amazon was a bookstore branching out in my head.)

    In fairness, I was a programmer and not an electrical engineer. And chargers back then weren’t exactly USB-C level smart. The barrel charger fit. I just thought “Oh, what a great deal. I’ll order these and get plaudits from my boss for saving money.” It wasn’t even my money.

    The other one is that when I was learning to code — I’m self-taught because everyone was back then — I used Vim and invented my own style. All my code was basically unformatted or, at best formatted consistently in a very non-standard way. That’s easy to fix nowadays where I can hit save and my code gets formatted automatically but it wasn’t so simple back then. I still feel bad for the engineer who followed me who had to fix that shit.

  • I have possibly the dumbest workaround to anything in history

     
            bindntr=CTRL,C,exec,hyprctl activewindow | rg -q "class: Wfica" && ( sleep 0.02 && hyprctl closewindow class:alacrittyclipboard ; alacritty -qq --config-file ~/.config/alacritty/alacrittyclipboard.toml --class 'alacrittyclipboard' --title 'Office 365 Desktop (SSL/TLS Secured, 256 bit)' -e sh -c 'sleep 0.03 && xclip -o | copyq copy - ; copyq clipboard | xclip -i' ) & ( sleep 0.2 && closewindow class:alacrittyclipboard )
    
        windowrulev2 = float,class:(alacrittyclipboard) 
    
        windowrulev2 = stayfocused,class:(alacrittyclipboard) 
    
        windowrulev2 = noborder,class:(alacrittyclipboard) 
    
        windowrulev2 = noanim,class:(alacrittyclipboard) 
    
        windowrulev2 = noblur,class:(alacrittyclipboard) 
    
        windowrulev2 = opacity 0,class:(alacrittyclipboard) 
    
        windowrulev2 = maxsize 1 1,class:(alacrittyclipboard) 
    
    
      

    allow me to explain this monstrocity... the clipboard in citrix workspace is broken in a stupid way

    it doesn't update the system clipboard unless you move focus away from the window... and out of focus windows can't update the clipboard for security reasons... this makes it so that if I hit ctrl c when citrix is open it opens a terminal window that's tiny, invisible and steals focus that essentially forces the clipboard to work.

    nonsense hack, but it works

  • I'm not sure if this counts because it wasn't intentional on my part, but... When I was a kid, my mom had a digital camera. The lense on it would extend when it was powered on, and then retract when it was powered off.

    At some point the lense got stuck, which caused the camera to not turn on properly and made it useless so she ended up getting a new one. I had gone to take the old/broken one to mess around with it and accidentally dropped it.

    Apparently the angle that it fell at was just enough to "lodge" the lense back into place yet the fall wasn't high enough to cause it to shatter or break. It worked perfectly after that, and while my parents were a bit upset they needlessly bought a new camera, they ended up letting me keep the old one.

    (Later on I figured that was their way of justifying not returning the new camera that probably had nice new features or something)

    I also vaguely remembering them saying something along the lines of "That's probably the only time in your life dropping a piece of equipment will actually fix it and was just luck - don't go trying that on other things randomly".

  • Lots of percussive maintenance going on around here, but one that sticks in my mind was testing some of the first 486DX PCs in 1990. One particular specimen from Compaq would only boot after hard power off by taking the lid off and tapping the CPU with a screwdriver. Worked fine after that.

  • Just thought of another one. I have an old Amiga 1200 which doesn't get powered up much but I accidentally dropped it in a move. Since then it's been prone to randomly crashing. Opened it up, nothing appeared to be dislodged. Somehow discovered that if I prop it up at an angle it doesn't crash any more.

  • "Power off, then on again." This was after a mystifying issue where the printer would do the invoice format and backgrounds, but refuse to print the text, and had a seasoned copier tech stumped. Still scratching my head on that one.

145 comments