And by "trouble running", I mean "the program doesn't launch at all, and I just stare at my desktop going...what happened?"
If anybody else has had the specific problem I'm about to explain, I have your specific solution.
Problem:
You run Rome.exe and nothing seems to happen. The computer will think for a few seconds, but then...nothing.
Then, because, why not?, you run Rome.exe again, and SQPR comes up, but the performance is poor. You get stutters in the opening video, and unexplained framerate dropouts in-game.
Solution:
Kill Rundll32
I run Win 7 Home Ultimate, and from time to time, when I run Rome (or a variety of other older .exes) they won't start. I've discovered this guy to be the culprit:
See Rundll32?
The solution works in this order.
With the task manager open, and the processes tab selected, and the processes itemized by CPU usage (as in the screen grab) Rundll32 will stay at the top of the list. It hogs 75-90% of your CPU.
Now, run your Rome.exe again.
When RomeTW (or whatever) pops up in the processes list, hit "End Process" for Rundll32.
Alternately, you can just wait until your game starts up completely, then alt+tab out and kill Rundll32.
I've found that if you kill Rundll32 before running the second instance of the game, Rundll32 just starts right back up.
If anybody knows of some stupid, simple fix for this problem that I haven't found, holler...but it just struck me today that this might answer some of the random threads talking about how SPQR won't start up, or doesn't run right.





Reply With Quote






