I have the problem as well, Im running XP Home SP2
AMD Athlon 64 3500
768mb ram
80gb and 160gb HDD
LiteOn DVD/CDRW combo

I have tried both CDs, changing compatabilty mode, making a CD image and mounting it with Deamon Tools, nothing seems to work. I have tred using a friends CDs and they dont work either. :cry:

I have SP1 and I would gladly try it since I have the cds right here in front of me, but I haven't installed it since oh 2000, does it require a key? I don't remember and the box is wayyyy far from me now and I HATE it when I install a game and I can't find my key.

I bought RA2 two years ago and have installed it twice. I tried to install it last week and I get the same "encountered a problem" message as mentioned above. Why won't it work now all of a sudden?

I don't have SP2 installed (XP Home is my OS), but I do have thirty-odd Windows updates, some of them installed as recently as February. Could this be the cause?

I have also bought the new Sold-Out edition of RA2 (I love this game, and didn't mind spending a bit of cash if a newer version was required). It does exactly the same thing.

What on Earth is going on ?!

I REALLY do want to get this game working again!

I have just uninstalled all the Windows updates added since November. I last played RA2 in January. It still won't install. I have no idea what else to try.

anyone with a solution, coz I have a similer problem

A poster on a different forum has suggested that updating your version of Direct X may cause problems. I installed DX9.0c about ten days ago, just to run 3DMark05. Previous to that I had DX9.0b installed (and RA2 DID run).

What do you reckon? Coincidence?

So, I have to downgrade it to .0b? Is that even possible? :blink:

same problem

Athlon XP 2500+
512MB Ram
40 GB HDD
Pioneer DVD619 52x

plz help. great game that i cant play. :ranting:

Nope, DX9.0c isn't the problem. A friend tried it out on his PC (which also has XP and DX9.0c installed) and it worked perfectly. I still have no idea why it's stopped working on my PC.

makes sense to run dxdiag on your machine and on his then, and see where the two outputs differ to see if you can work out the difference(s).