• Something Burger 🍔@jlai.lu
    link
    fedilink
    arrow-up
    44
    ·
    8 months ago

    All modules that call a Unix library contain WoW64 thunks to enable calling the 64-bit Unix library from 32-bit PE code. This means that it is possible to run 32-bit Windows applications on a purely 64-bit Unix installation. This is called the new WoW64 mode, as opposed to the old WoW64 mode where 32-bit applications run inside a 32-bit Unix process.

    🦀🦀🦀

    • BlanK0@lemmy.ml
      link
      fedilink
      arrow-up
      26
      ·
      edit-2
      8 months ago

      So in the future no need to install 32 bit packages of wine in a 64 system??? 👀

      • OsrsNeedsF2P@lemmy.ml
        link
        fedilink
        arrow-up
        26
        ·
        8 months ago

        Correcto. Which means Steam will probably drop 32 bit libs soon. Which means Ubuntu will stop shipping 32 libs. The era is truly coming to an end

    • henfredemars@infosec.pub
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      8 months ago

      Come on Steam, show those 32-bit libs the door!

      Not the political kind. The shared object kind.

      • CalcProgrammer1@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        Does this change run the 32-bit .exe using x86_64 instructions? From the description it just sounds like it allows 64-bit Linux libraries to be used in place of 32-bit ones, but that the Windows layer still operates in native 32-bit mode. This means there is still a need to emulate 32-bit x86 instructions which I don’t think box64 can do at this time (x86_32 translates to arm32 with box86, x86_64 translates to arm64 with box64). If box86 could translate x86_32 to arm64 then this might work as Wine would handle the conversion between 32 and 64 bit addressing and argument passing into the libraries but I’m not familiar with the inner workings there.