What was the reasoning behind splitting "Program Files"

>>57694151
so you can have a 32bit and 64bit version of the same program at the same time

a stranger thing is how "system32" is where 64bit libraries go in 64bit windows, and 32bit libraries go in "syswow64", and both kinds of programs believe they're accessing "system32"

File: k.jpg (86KB, 772x730px) Image search: [Google]

86KB, 772x730px

To easily separate 32 and 64 bit applications.

It's just a way to split up 32/64.

On Linux:
32bit host: lib/
64bit host: lib/
64 with 32 support lib/ and lib32/

On Windows:
32bit host: Program Files
64bit host (always has 32b support): Program Files and Program Files (x86)

>>57694246
Oh and the reason is obvious, duplication. Perhaps you want/need both architectures installed and if you put them in the same prefix you have to do some wacky renaming, symlinkig, etc and cause a huge fucking mess, it's just a bad idea.

>>57694246
>(always has 32b support): Program Files and Program Files (x86)
64bit windows PE is 64bit-only

>>57694151
A better question is why they named the folder "Program Files" instead of just "Programs" (and then "Programs32" or something)

>>57694151
Triggering autistic neets

>>57694351
not to mention that some programs refuse to have spaces in their file path, so they install in C:\ thus completely removing the point of Program Files and Program Files(x86)

>>57694302
Yes, but I mean generally the installed OS comes with 32bit support (WOW64 x86 emulator) as default.

This is why they should just throw away all existing software once a decade and start over from scratch

>>57694246
Program Files (x86) is 32 bit applications
Program Files is for 64 bit
Fixed

>>57694502

That hasn't been an issue since like the 90s.

>>57694302
Windows Pajeet Edition? Or is it Windows Poo Edition?

>>57694833
>tfw itanium will never be a thing

Linux 32:
    /usr/lib                (32)

Linux 64:
    /usr/lib                (64)

Linux 64 with 32 support:
    /usr/lib                (64)
    /usr/lib32              (32)
    
    
Windows 32:
    \Program Files          (32)
    
Windows 64:
    \Program Files          (64)
    \Program Files (x86)    (32)

>>57695519
wat about
>>57694302

>>57695650
There's no 64bit-only in windows 64bit unless 32bit is deprecated which is almost impossible.

>>57695343
pre-installation environment
aka, the windows that runs during windows setup

try it, boot up a 64bit windows install dvd in a VM or whatever, hit shift+f10 to bring up cmd, then try to run a 32bit program (note: not all programs will work in PE, it's a pretty bare version of windows, i know 7-zip works, and it has 32 and 64bit versions)

>>57695343
pre-installation environment
aka, the windows that runs during windows setup

try it, boot up a 64bit windows install dvd in a VM or whatever, hit shift+f10 to bring up cmd, then try to run a 32bit program (note: not all programs will work in PE, it's a pretty bare version of windows, i know 7-zip works, and it has 32 and 64bit versions)

>>57695679
So how are there pure 64-bit environments in Linux?

>>57694302
Yeah but realistically WinPE is mostly used for installation media and PXE booting so that's not a big deal.

Unless you need a 64bit PE instance with a 32bit driver, that's always fun.

>>57695343
pre-installation environment
aka, the windows that runs during windows setup

File: [011403].jpg (19KB, 620x363px) Image search: [Google]

19KB, 620x363px

>>57694151
This board is littered with children, I'm outta of my mind coming here everyday.

>>57694246
*/lib/ and */lib64 folders are more similar to system32/syswow64

It's /usr/bin that is more like program files

>>57695793
Because linux is hobby OS.