1868
Comment on a YT video about Windows on ARM (lemmy.world)
submitted 2 years ago by to c/linuxmemes@lemmy.world
228 comments fedilink hide all child comments
 

Installing OS, 10 years ago:

Windows: click a couple of buttons enter username and password

Linux: Terminal hacking, downloading shell scripts from github

Installing OS today:

Linux: click a couple of buttons, enter username and password

Windows: Terminal hacking, downloading shell scripts from github.

Link to video: https://m.youtube.com/watch?v=qKRmYW1D0S0

you are viewing a single comment's thread
view the rest of the comments
[–] 59 points 2 years ago (7 children)

Windows tries to obfuscate any useful information while Linux tries to give logs and man entries to walk the user through what went wrong.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 32 points 2 years ago

    As a part-time sysadmin at my small company. We use Altium and Solidworks, so we need windows.

    I have 10x more windows problems than Linux problems like a bug for around 5 or so people where a windows update would disable the microphone, but every single microphone menu and setting would say it is enabled and working properly. You HAD to use their troubleshooter (which they are now phasing out, wtf) in order for it to be auto fixed. So soon it will probably be replaced by something else that won't fix the issue.

    0 information online about it, 501 different way to fix audio issues, none of which work.

    Nowadays the only problems that I have with Linux are slight bugs or user errors, honestly.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 15 points 2 years ago (5 children)

    When the BSOD code has nothing to do with your actual problem

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 32 points 2 years ago (4 children)

    Well OBVIOUSLY you need to set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session\Windows\Microsoft\Win10\MSWindows\CockNBalls\BSODWord to 0 then restart your computer.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 7 points 2 years ago (1 child)

    Sorry, that was before KB1103995. The new method requires you to check a box in your OneDrive account first before the entry is respected.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 2 years ago

    Except you already have that update installed, the box is not checked and the entry is still respected, nobody could possibly tell you why because that's not how it's supposed to work and everyone else works as stated! And now you have to live with the knowledge that your system is in some unobserved quantum superposition with a critical fix in place which may stop working at any moment for any reason and nobody can tell you how you even managed to get into this situation...

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 years ago*

    You forgot that you also need to create a new 32bit word entry with the value of the amount of system RAM in gigabytes times 2 divided by the square root of your age times 10.

    Otherwise BSODWord won't be picked up.

    Edit: also you need to redo that every time your system updates because Windows update will reset all those values

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 years ago*

    NOOOOOO please you're reawakening 20+ years of accumulated Windows trauma 😭 😭 😭

    That was so confusing and stressful I don't know how I --or anyone-- survived the mental strain of regularly troubleshooting Windows

  • permalink
  • fedilink
  • source
  • parent