• jj4211@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      11 months ago

      He might have oversimplified to assume it was the 32-bitness that is the problem. Could be an ancient Windows Driver Model version that is no longer supported. Could have been that there were no signed drivers, or at least no drivers that are signed in a way that would pass today.

      The thing is that Windows banks on extended binary driver compatibility for running “old” hardware, but breaks that compatibility ever so often, and they don’t have first-party investment in drivers for hardware and third-parties would eschew standard multiple device drivers that would have worked fine in favor of their own branded driver/app experience. In Linux, mostly those devices get covered by generic multi-vendor drivers that are better maintained.