• 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: November 1st, 2023

help-circle
  • Sounds like the drive is dead. They are mechanical devices which tend to wear out with use. Literally magnetic platters spinning at 7200rpm with heads floating on a cushion of air a few microns above the surface. Just a single speck of dust that gets in there can absolutely destroy the drive, as can moving it while it’s spinning, or it could have a manufacturing defect that causes it to prematurely fail for no other reason whatsoever.

    The best you can really hope for is that the drive is still covered under warranty and get it replaced by Western Digital.


  • Your machine is compromised, so the hackers are simply stealing the post 2FA session tokens from your computer. Basically, once you enter your password and complete the 2FA challenge, the server grants an access token to your computer so you don’t need to repeat the process for every interaction with that service. If there is malware on your computer, those tokens can be stolen and reused by nefarious actors.

    2FA isn’t a foolproof system; it just makes it significantly harder for hackers to log in. And they’re basically piggybacking on your successful login to hijack your accounts.

    Format the machine and change *all* your passwords.

    (And don’t let your little brother use your computer again)




  • Speeds between two computers is as fast as the slowest link. If they’re both on the same local network, the bottleneck will not be your ISP. If they’re hard-wires, it will be limited by the gigabit connection. If one or both are on the wireless network, the bottleneck will be the speed that they can get over WiFi (which will depend mostly on distance, congestion, and interference)




  • Not without a debugger and the knowledge to know how to use it as well as knowledge of what normal operation of the program looks like under the debugger.

    But when a program is “not responding” what that means is that the message pump loop from Windows is not progressing. Basically, every interaction between the Windows desktop and the program goes into a queue that the program picks up and processes. These are things like mouse clicks, key presses, window being moved or resized, etc. If the queue keeps growing, windows assumes the process is stuck and it’s usually correct for well written programs.

    But when programs do something stupid like not use a separate UI thread and background processing thread, then things get messy and you see this behavior even when the program is operating “normally”