It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
DavesGaming: Rumor has it that Windows 11 will not run 32-bit apps/games once it releases. Assuming this becomes true, how will that impact GOG games? Seeing how GOG has brought us older games that (I assume) don't use 64-bit.

Unless I'm mistaken & I/we have nothing to worry about.
That means that only Windows 64 bit version will be available and the 32 bits operating system will be deprecated. But Windows 64 bits should run perfectly 32 bit apps.

For example I am sure that a majority of people uses a Windows 10 64 bit version and they are able to run 32 programs whithout any problem.
avatar
DavesGaming: Rumor has it that Windows 11 will not run 32-bit apps/games once it releases. Assuming this becomes true, how will that impact GOG games? Seeing how GOG has brought us older games that (I assume) don't use 64-bit.

Unless I'm mistaken & I/we have nothing to worry about.
STOP ALL THIS BULLSHIT ABOUT WINDOWS 11.

https://en.wikipedia.org/wiki/WoW64
avatar
Crosmando: Are there any indications as to how much the architecture is going to change in Win11? Will programs that work in Win 10 be guaranteed to work in Win 11?
As far as in aware, there isn't that much of a difference between 11 and 10 under the hood. It's more or less the same code, so there shouldn't be any major issues regarding software. 11 is not to 10 what Vista was to XP.
avatar
KingofGnG: STOP ALL THIS BULLSHIT ABOUT WINDOWS 11.

https://en.wikipedia.org/wiki/WoW64
Right, something else should be addressed
Post edited July 06, 2021 by patrikc
avatar
Crosmando: Are there any indications as to how much the architecture is going to change in Win11? Will programs that work in Win 10 be guaranteed to work in Win 11?
Based on the latest build available. Windows 11 is literally Windows 10 with a new coat of paint on the UI and some extra technical requirements (e.g. TPM 2.0)

At least for now that is, nobody knows how it will be in 2 or three years.
It seems pretty obvious what to expect.

Unless MS planned on doing a 180 in this department, they gain nothing by bringing the topic up. They haven't brought it up.
avatar
drmsux: It seems pretty obvious what to expect.

Unless MS planned on doing a 180 in this department, they gain nothing by bringing the topic up. They haven't brought it up.
One of the several reasons I cannot be bothered with Microsoft products anymore.
avatar
DavesGaming: Rumor has it that Windows 11 will not run 32-bit apps/games once it releases. Assuming this becomes true, how will that impact GOG games? Seeing how GOG has brought us older games that (I assume) don't use 64-bit.

Unless I'm mistaken & I/we have nothing to worry about.
If you think about it, 32bit support does hold back the OS to a degree, because you're doing compatibility. Honestly if you do a VM with say XP on it, you could run 99% of your 32bit games/programs with no issues.

To do 32bit support in Linux and Windows, they basically have a paralell OS running, since to do any system calls or any at all, the 64bit doesn't translate to 32bit space, so libraries need 32bit ones. Dropping all 32bit support sounds bad, but at the same time it may be useful. Though the sudden 'this doesn't work' would be annoying.
avatar
rtcvb32: To do 32bit support in Linux and Windows, they basically have a paralell OS running, since to do any system calls or any at all, the 64bit doesn't translate to 32bit space, so libraries need 32bit ones. Dropping all 32bit support sounds bad, but at the same time it may be useful. Though the sudden 'this doesn't work' would be annoying.
WoW64 doesn't use much space or cause performance issues when running x64 applications. Given it just works in Windows, I don't really see why you would depreciate it.

Virtual machines are a bit of a ball ache when it comes to gaming (which are the x86 applications most people would want to keep running), especially when you get to the final games of the 32 bit era.

Let's be honest, if MS drop WoW64, someone will just end up coding an equivalent and all will be well in the world again.
avatar
rtcvb32: To do 32bit support in Linux and Windows, they basically have a paralell OS running, since to do any system calls or any at all, the 64bit doesn't translate to 32bit space, so libraries need 32bit ones. Dropping all 32bit support sounds bad, but at the same time it may be useful. Though the sudden 'this doesn't work' would be annoying.
avatar
pds41: WoW64 doesn't use much space or cause performance issues when running x64 applications. Given it just works in Windows, I don't really see why you would depreciate it.

Virtual machines are a bit of a ball ache when it comes to gaming (which are the x86 applications most people would want to keep running), especially when you get to the final games of the 32 bit era.

Let's be honest, if MS drop WoW64, someone will just end up coding an equivalent and all will be well in the world again.
Deprecate not depreciate?
avatar
pds41: Let's be honest, if MS drop WoW64, someone will just end up coding an equivalent and all will be well in the world again.
Like making a BusyBox for windows, but to run older versions?
I got invited to test the insider build. Very tempting. Maybe tomorrow after work I'll take the plunge....
avatar
pds41: WoW64 doesn't use much space or cause performance issues when running x64 applications. Given it just works in Windows, I don't really see why you would depreciate it.

Virtual machines are a bit of a ball ache when it comes to gaming (which are the x86 applications most people would want to keep running), especially when you get to the final games of the 32 bit era.

Let's be honest, if MS drop WoW64, someone will just end up coding an equivalent and all will be well in the world again.
avatar
nightcraw1er.488: Deprecate not depreciate?
Yes - bit of a typo there!
avatar
rtcvb32: If you think about it, 32bit support does hold back the OS to a degree, because you're doing compatibility. Honestly if you do a VM with say XP on it, you could run 99% of your 32bit games/programs with no issues. To do 32bit support in Linux and Windows, they basically have a paralell OS running, since to do any system calls or any at all, the 64bit doesn't translate to 32bit space, so libraries need 32bit ones. Dropping all 32bit support sounds bad, but at the same time it may be useful. Though the sudden 'this doesn't work' would be annoying.
I think the 32-bit support impact is way overestimated. SYSWOW64 folder on mine adds up to barely 1.4GB max (or barely 1/10th of the install size). And that's after adding virtually all 32-bit .NET, VCRedist, etc, dependencies. The bulk of Windows bloat by far comes with W10's UWP crap. Hence why W7 ISO size (supports both 32 & 64 bit but not "new" W10 UWP apps) was significantly smaller than "streamlined" Windows 10X (which completely removes all 32-64 bit "legacy" support and just runs UWP). By far the biggest thing of all adding bloat to Windows is Microsoft's "vision" of wanting the Microsoft Store to become the Google Play Store for desktop and the doubling down on UWP API to enable that.