5 ms·

And for more fun: -- C:\Windows\System32 contains 64 bit binaries, while -- C:\Windows\SysWow64 contains the 32 bit ones (that is on a 64 bit version of Win

by malkia 14y ago

And for more fun: -- C:\Windows\System32 contains 64 bit binaries, while -- C:\Windows\SysWow64 contains the 32 bit ones (that is on a 64 bit version of Windows) Then the naming of $(Platform) $(PlatformShort) in MSVC IDE.. Explore for yourself - it's fun, it's even more fun when the windows sdk, dxsdk, and other ms's sdk's use different naming conventions for the same things. Or the WinDir vs SystemRoot it's something about Microsoft creating too much confusion with their naming

Gormo 14y ago
These are hardly problems. Users don't generally encounter system directories or identifiers in IDEs, and these patterns have emerged from MS's traditional dedication to maintaining backward compatibility, which is usually much more important to developers and power users than having directory names be completely descriptive of what's in them. The problem with Windows RT is exactly the opposite: they've broken backward compatibility, severely, and created a product that bears no resemblance to what the vast majority of users recognize as Windows, yet they've decided to call it "Windows" anyway.
- malkia 14y ago
  most often, it's us developers becoming users of some other software. And real users are puzzled sometimes, there were at least couple of emails to the sqlite mailing list about missing sqlite3.dll from users. In one case it was some tax program installing it in the system32 folder, messing it up with another one (why would they do that is another matter), also as someone posted below, there is Program Files, and Program Files (x86), but there apps that do not follow that convention (internally they have their own bin32, bin64 folders), and it comes to users again - usually plugins for various creative suits - audio, video, etc.
chris_wot 14y ago
WoW64 stands for Windows 32-bit on Windows 64-bit. It's a subsystem that allows backward compatibility. Windows on Windows allowed 16-bit software to run on 32-bit Windows. At the time there was no need to call it WoW32. I suppose Microsoft could have called WoW64 W32oW64, but they didn't.
revscat 14y ago
While you're on the subject, perhaps someone could explain why there are separate "\Program Files" and "\Program Files(x86)" directories.

by malkia 14y ago

Gormo 14y ago

These are hardly problems. Users don't generally encounter system directories or identifiers in IDEs, and these patterns have emerged from MS's traditional dedication to maintaining backward compatibility, which is usually much more important to developers and power users than having directory names be completely descriptive of what's in them. The problem with Windows RT is exactly the opposite: they've broken backward compatibility, severely, and created a product that bears no resemblance to what the vast majority of users recognize as Windows, yet they've decided to call it "Windows" anyway.

malkia 14y ago
most often, it's us developers becoming users of some other software. And real users are puzzled sometimes, there were at least couple of emails to the sqlite mailing list about missing sqlite3.dll from users. In one case it was some tax program installing it in the system32 folder, messing it up with another one (why would they do that is another matter), also as someone posted below, there is Program Files, and Program Files (x86), but there apps that do not follow that convention (internally they have their own bin32, bin64 folders), and it comes to users again - usually plugins for various creative suits - audio, video, etc.

chris_wot 14y ago

WoW64 stands for Windows 32-bit on Windows 64-bit. It's a subsystem that allows backward compatibility. Windows on Windows allowed 16-bit software to run on 32-bit Windows. At the time there was no need to call it WoW32. I suppose Microsoft could have called WoW64 W32oW64, but they didn't.

revscat 14y ago

While you're on the subject, perhaps someone could explain why there are separate "\Program Files" and "\Program Files(x86)" directories.