• Amanda@aggregatet.org
    link
    fedilink
    English
    arrow-up
    15
    ·
    4 months ago

    Interesting! Do you have a link to a write up about this? I don’t know anything about the windows memory manager

      • AnyOldName3@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 months ago

        It’s a silly flag to use as it only works when running 32-bit Windows applications on 64-bit Windows, and if you’re compiling from source, you should also have the option to just build a 64-bit binary in the first place. It made a degree of sense years ago when people actually used 32-bit Windows sometimes (which was usually just down to OEMs installing the wrong version on prebuilt PCs could have supported 64-bit) if you really wanted to only have one binary or you consumed a precompiled third party library and had to match its architecture.

        • wizardbeard@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          3
          ·
          4 months ago

          You can also toggle it on precompiled binaries with the right tool (or a hex editor if you’re insane), which was my main use case. Lots of old games that never got 64-bit releases that benefit from having access to the extra RAM, especially if you’re modding them. It’s a great way to avoid out of memory crashes.

    • ArbiterXero@lemmy.world
      link
      fedilink
      English
      arrow-up
      18
      arrow-down
      1
      ·
      4 months ago

      Intel PAE if the answer, but it still came with other issues, so 64 was still the better answer.

      Also the entire article comes down to simple math.

      Bits is the number of digits.

      So like a 4 digit number maxes out at 9999 but an 8 digit number maxes out at 99 999 999

      So when you double the number of digits, the max size available is exponential. 10^4 bigger in this case. It just sounds small because you’re showing that the exponent doubles.

      10^4 is WAY smaller than 10^8

    • neclimdul@lemmy.world
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      2
      ·
      edit-2
      4 months ago

      It was actually 3gb because operating systems have to reserve parts of the memory address space for other things. It’s more difficult for all 32bit operating systems to address above 4gb just most implemented additional complexity much earlier because Linux runs on large servers and stuff. Windows actually had a way to switch over to support it in some versions too. Probably the NT kernels that where also running on servers.

      A quick skim of the Wikipedia seems like a good starting point for understanding the old problem.

      https://en.m.wikipedia.org/wiki/3_GB_barrier

      • Amanda@aggregatet.org
        link
        fedilink
        English
        arrow-up
        12
        ·
        4 months ago

        Wow they just…disabled all RAM over 3 GB because some drivers had hard coded some mapped memory? Jfc

        • ms.lane@lemmy.world
          link
          fedilink
          English
          arrow-up
          11
          ·
          4 months ago

          Only on consumer Windows.

          Windows Server never had the problem. But wouldn’t allow Creative Labs drivers to be installed either…