LINUX SUPPORT IS HERE

[rootbeer23]

why not just
$ wine steam.exe

that doesnt work?

[Frozen_byte]

On some cases you need to purge your whole Wine, so tatsus way is the "brutal" one.
Usually it is enough to install Steam.exe

Anyway: Why do you install Steam + FAF? It's obviously a waste of ressources because Steam.exe AND FAForever.exe AND ForgedAlliance.exe will eat your CPU. In my opinion it is smarter to bypass steam and install Forged Alliance by an ISOfile. :ugeek:

[rootbeer23]

On some cases you need to purge your whole Wine

why?

[Frozen_byte]

Because it's a wired thing. Wine is one of the most awesome random-problem-generators I've ever heard from.

No seriously, may he has corrupted/old files and tried to "reinstall"; that is not always gonna working.

[rootbeer23]

whatever his original problem is...
But not even describing the original problem and suggesting a format c: style solution
to whatever it is that may or may not need fixing is not smart.

[tatsu]

yes.

note the above.

I do prefer the nowinetricks approach but I can't seem to do it as I did before.

libraries now refuse to install under the stock wine 1.7 because it is 64bit (even though it has 32 and 64bit program files folders)

[tatsu]

On some cases you need to purge your whole Wine, so tatsus way is the "brutal" one.
Usually it is enough to install Steam.exe

Anyway: Why do you install Steam + FAF? It's obviously a waste of ressources because Steam.exe AND FAForever.exe AND ForgedAlliance.exe will eat your CPU. In my opinion it is smarter to bypass steam and install Forged Alliance by an ISOfile.

steam fa is the way to go on windows as well.

the fact is I save up a lot of time on install by copying the FA folder over. Only steam can allow you to do this and have a working program. (also steam's FA is smaller disk-size wize for a number of reasons, as I happen to run the whole on a 60GB SSD I try to keep things tight and steam doesn't make me catch up to the ISO install's size)

steam however does not need to be running for FAF FA to run.

remember, faf uses it's own executable + the original files in FA install folder.

it only requires FA to be correctly installed and have had a first run, not for it to be running

[rootbeer23]

try wine1.7-i386

[tatsu]

try wine1.7-i386

I'll do that.

[tatsu]

whatever his original problem is...
But not even describing the original problem and suggesting a format c: style solution
to whatever it is that may or may not need fixing is not smart.

the original problem is that you cannot simply uninstall your program, install another wine and try to install it there.

wineprefix and wine somehow keep a memory of what they've done and will f*** your install up, or insist on putting it in a certain wine even though you were specific about not wanting it there.

to make 'em shut up you have to start clean.