Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Are you talking about the RAM patch? Because I think you are misunderstanding its use. The reason why you have to install it is when you are on Windows Vista/7/8 and have more than 2gb of RAM, the engine for FoC doesn't like that for some reason and must be told to allow it. It is probably safe to assume that OP has more than 2gb of RAM, so yes... that calls for the RAM patch, but you should make sure that you understand and let others understand why it is used.
I believe the guy above was talking about the RAM patch, which is already integrated into the Steam version. However, the game itself has had a 50-50 chance for people getting it to work on their Windows 8.1 setup. Someone on here awhile ago said that the OS has no problem with it, which means that it boils down to some user config/updates or SOMETHING that everyone having trouble has in common. So anyway... it's a toss-up, it might work and it might not. Sorry I cannot give you a better answer, but without Windows 8 myself I cannot test and figure out the problem. I know the first thing I would do is test the game as soon as the OS was installed, install Steam and then EaW and try it... if it works before updating but then not after... that means it has something to do with Windows Updates. If it still works... slowly load up all the programs you want, checking the game after each one... I am just shooting troubleshooting ideas to you. That is what I would be doing if I had Windows 8. I am surprised no one else has done so... that is the only way to figure out what the problem is, without diving in real deep into error codes, but then even then that might lead you nowhere.