I don’t know why I even bother opening the settings app

  • doctorcrimson@lemmy.world
    link
    fedilink
    arrow-up
    21
    ·
    edit-2
    1 year ago

    According to Dave Plummer, a retired Windows Engineer, there are actually bugs in some of the windows components because he intended for them to be temporary solutions, like the CPU or Hard Drive usage numbers had to be Massaged to be lower than 100%, for example. When the Task Manager doesn’t respond you can actually use Ctrl+Shift+Esc to queue up a new Task Manager if the old one doesn’t revive itself. That stuff hasn’t changed since 1996.

    He also wrote the File Formatter, which has a file size limit of 32Gb for the Fat32 format for the same reason: it wasn’t supposed to be permanent, but it hasn’t changed for over 20 years. The concept at the time was that Cluster Slack would make a large drives like a terabyte more than 99% wasted space in the format, so 32Gb was arbitrarily chosen as a limit.

    • foobaz@lemmy.world
      link
      fedilink
      arrow-up
      10
      ·
      edit-2
      11 months ago

      fyi Dave was involved in some scareware bullshit as one of the main actors and sued for it. Fuck this guy.

    • jasondj@ttrpg.network
      link
      fedilink
      arrow-up
      9
      ·
      1 year ago

      I went to go disable my nic.

      It needed a reboot to take effect.

      The fuck? I only want to turn it off because I’m testing something and I need a change of ip to test an application and I’m feeling lazy, so I turn off the nic to go to wifi. Good enough? Nope.

      So stand up and unplug the cord.

      Cool. Switched over. Test didn’t work as expected. Plug cord back in.

      Next day computer reboots for updates and I’ve got no internet. Go crazy trying to figure out what it was then remember it needed a reboot to disable the nic.

    • EddoWagt@feddit.nl
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      He also wrote the File Formatter, which has a file size limit of 32Gb for the Fat32 format for the same reason: it wasn’t supposed to be permanent, but it hasn’t changed for over 20 years.

      I was thinking about this recently, so it is a bug, not a feature

      • doctorcrimson@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I mean, it was intentional in a way, so the definition of bug is hazy, but the functioning version would be the ExFAT format.

        • EddoWagt@feddit.nl
          link
          fedilink
          arrow-up
          2
          ·
          11 months ago

          But the problem isn’t in Fat32 itself, as you can format larger disks in that format just fine

          • doctorcrimson@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            11 months ago

            Yes, the final line of my comment explains that, it’s just that the cluster size in Fat32 has a lower bound so if you have files smaller than the cluster then they take a whole cluster, and that can lead to cluster slack that is vast majority wasted space.

      • Galaxy@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 months ago

        The limit on formatting drives as fat32 is 32GB on windows though anything above 32GB and you have to go find a 3rd party tool to convert larger disks to fat32

    • jasondj@ttrpg.network
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      I went to go disable my nic.

      It needed a reboot to take effect.

      The fuck? I only want to turn it off because I’m testing something and I need a change of ip to test an application and I’m feeling lazy, so I turn off the nic to go to wifi. Good enough? Nope.

      So stand up and unplug the cord.

      Cool. Switched over. Test didn’t work as expected. Plug cord back in.

      Next day computer reboots for updates and I’ve got no internet. Go crazy trying to figure out what it was then remember it needed a reboot to disable the nic.