Actually, I find that having the game windowed leads to less problems (not to mention, improved performance). Here are some other miscellaneous tips that come to mind:
- On newer machines, it also helps to avoid opening any in-game menus for an extended period of time (more than a few seconds).
- Some mods like DSL commonly show Not Responding messages but they usually go away if you wait.
- If improperly installed or created, mods can also cause RA2 to crash unnecessarily.
- After opening a bot in the Robot Workshop, try not to load another bot immediately.
- If an event is causing your game to crash, you can either terminate the event or fix the underlying issue. I don't recall ever attempting to diagnose this error (I don't see it very often because I don't do very many events) but I'm pretty sure it has something to do with incorrect data being written to either the bot file or the Teams.txt.
It is not possible to fix these bugs without the source code of RA2. It is, however, pretty easy to avoid them.
