ORIGINAL: burroughs
...since I really does not have the slightest idea what does tat mean that " ... the Windows "not responding" message doesn't necessarily indicate a problem. ..." And the stop signs does not necessarily mean that you have to stop or what?
If you dial a phone number and get a busy signal do you assume that the phone system is malfunctioning? Because that is really what the message means. It means that the program is busy doing something and can't respond to your interrupt request. And two examples of this for TOAW are the interturn calculations and combat execution. If you try to get TOAW to respond while those actions are going on, you will get that message. For the benefit of anyone reading this thread, if not burroughs, I hope that is understood.
I thought that I described the issue in quite a detailed manner.
You didn't. I can't reproduce the problem and I don't know just what you did that might have caused it, or what your computer may have been doing when it happened.
It would also be good to assume that I may have the slightest idea what I am aiming at and checked such basic stuff as the machine load, processes in the background and so on - and that is why I did not described that in length. I just assume somebody else is not stupid - but may be. Wise men see the wise around, fools can see only other fools.
Yet you make statements like the one at the top that seem to indicate that you're clueless. Computers are very complicated machines. It's easy to misunderstand or overlook something.
And Lobster, my friend, if you were as good at reading as I am , you would perhaps have noticed that Telumar wrote about at least one more guy who is also experiencing that so with up to apparently seven people participating in this discussion over 50 % is affected by the issue recurrence. Am I also blame some vague misconception for that, Mr. Lemay?
My comments apply to Stefan as well. We don't know if what he is experiencing is due entirely to Win7. We do know that Win7 has exactly these sorts of issues with many programs other than TOAW. For that reason, it is not surprising that more than one user may be reporting a similar issue - it may still have nothing to do with TOAW.


