StargazingDog
Warlord
I'm surprised Windows hasn't moved to binary "packages" like on the Mac. Mac programs have every possible executable available in one file (PPC, Intel, 32bit, 64bit).
I personally don't get why Windows splits these directories up, there is no reason for it, but I assume it is convenience or something stupid like that. That being said, a 64bit application could easily be run from the "Programs Files (x86)" directory, you'll just have to tell Windows it is 64bit, which Steam will do for you.
thank you! Now just git rid of the needing steam (or any kind of DRM) and I will buy. Untill then I will not buy.
So tell me how does this happen? How i can run Crysis in 64bit mode from "Program Files (x86)" folder?
And what does steam had to do with 32bit or 64bit?
Im asking these questions because i dont know these things, i only know that Crysis refuses to start 64bit mode from "Program Files (x86)" folder.
I honestly am not sure. Have you tried right clicking the file and checking its properties. I am not an expert on Windows, only its flaws, not actual usage!
The main difference is you can use more RAM (random access memory) if you have the 64 bit version. I think 32 bit limits you to 3 gigs, while 64 bit lets you take so much that you wont have to worry about the limit until years into the future.
The requirements haven't been published anywhere yet.BTW, I've been searching for hardware requirements and can't find them.
I have an old Lenovo Thinkpad T61p that is most likely up to the job of running Civ5 but I'm curious how close to the bottom end of the requirements I'm getting.
So steam says where it installs the game and we cannot change that, steam also runs it "how its supposed to run"
If steam installs the steammap (or whatever) in Program Files (x86) folder, (where by default everything goes in 64bit windows if you ask from me,) then there is no point for Firaxis to make 64bit version of the game cause it wouldnt be able to start from that directory. If it installs the steammap in somewhere else then couldnt there be some compability issues with 32bit program forced to operate in 64bit mode?
I'm surprised Windows hasn't moved to binary "packages" like on the Mac. Mac programs have every possible executable available in one file (PPC, Intel, 32bit, 64bit).