Quote:
|
Originally Posted by Marshall7a
There's no call for that. I was merely trying to illustrate a point, that any device of the same type but not the same construction can act differently.
Whilst I concur that it is unlikely to be a problem with the processor, it could be an issue with the operating system vs 32-bit emulation on that processor. Again, unlikely but still possible. It is more likely an issue with the particular setup of the operating system and related drivers, etc - I know loads of people who have trouble with YR on XP, and I know a few people who can ONLY get it to work on XP.
As for YR vs RA2 - they are different executables with different code. You only have to play one game of each to see how vastly different the look and feel of the two games are.
I equally know lots of people who have trouble with one but not the other.
Ultimately, RA2/YR was not designed for XP becuase it wasn't around at the time.
I suggest trying variations on compatability mode, try updating drivers, and, failing that, you'll have to look at clean installing your OS.
|
My apologies, it hasn't been the best day ever.
While I understand your regards to different executables and so forth, it shouldn't cause such a processor problem like what may be happening simply due to the nature of the game being built on the same engine in which processor specs wouldn't change inside the games build. Then again, stranger things have happened.
While I understand RA2/YR not being designed for XP, XP is (so far) the most compliant friendly of the operating systems to date and shouldn't be causing such a drastic issue. The real question would be does he have problems with other games in a similar way or is it simply RA2/YR?
