2.2.3 crash with vista :S

[-Kosh-]

I fixed it so the savegame delete routine works correctly. This avoids the problem.
http://developer.wz2100.net/ticket/981

[topo1948]

I do not understand what you want?
From what you posted before you said that your OS crashed. WZ can not do this. It does not have ring 0 or ring 1 access like drivers.
That is why I said that your system is at fault, it could be drivers, RAM, or overheating. I have no way to know, only you can test to find out.

i-NoD wrote:Hmm... everyone is sooo concentrated on drivers crash idea. How about both crashes were caused by wz state machine corruption? Look on the savegame name: it has sometrailing spaces that will fail saving routine (on Win at least). Just try to create such a save: it will fail, BUT a .gam fill still exists (can't be removed after the fail). If I try to load this game in front menu it'll fail and return on the main screen, if start structure limiter screen after it'll instantly crash-to-2 without any .RPT dumps Starting a new game will result in a zero power level and probably lead to a similar-to-1 crashes from other non-visible corruptions.
Seems like we need to trim whitespaces during saving games, but there is a problem that we can't override a savegame for now.

-Kosh- wrote:

Code: Select all
C:\Program Files\Warzone 2100\warzone2100.exe caused an Access Violation at location 77b17dd2 in module C:\Windows\system32\ntdll.dll Writing to location 00000010
Call stack:
77B17DD2 C:\Windows\system32\ntdll.dll:77B17DD2 RtlEnterCriticalSection
1000587E C:\Windows\system32\OpenAL32.dll:1000587E alcCaptureOpenDevice
...
77AFA85F C:\Windows\system32\ntdll.dll:77AFA85F RtlExitUserProcess
77C73B69 C:\Windows\system32\kernel32.dll:77C73B69 ExitProcess
6993145F C:\Windows\system32\nvoglv32.dll:6993145F DrvPresentBuffers


That is kernel level. WZ can not cause this, it is driver related.

This it's what I means.
There are people with problems and a smart group searching for solutions. Common goal , WZ get better every day.
Is fascinating reading as you analyze situations among those who know about, by reference to reports, discussing with different points of view. Looking to find the problem and solve it, always find a solution.
I make it clear . When you have all the background required for the analysis.
Secondly, in regard to my problems. Following the forum I realized that I never give minimal information, only a single complaint or regret.
Something is obvious. we need a common language. I do not mean particular language (Spanish, French or Russian)
Just a thought.
Information crucial to analyze and seek solutions. How and where to get it to send them.
As i said before, single complaint or regret do not helps.
I not talking about bug reports, ticket, etc. Only give to you the information required to analyze and determine the causes of the problem.
We have an obligation not to waste time with those who know. At least learn to express our problems in the language requested by you.Let us help solve our problems telling us how and to contribute to fix.

This kind of things give you clues. how and where you get it.

if we look at the beginning of this, the quote ones and compare whith the normal problems report done by normal people. There are two worlds apart, look for a bridge of communication.
I'm sure many people are just playing Wz. Most of them without knowing how a game works, just play.
I read about Warzone 2100 publicity. Excellent Idea.
This forum it's about make Wz. better. most people here care about, not just play Wz. Try to exploit the problems posed by those who do not know, creating the tools. So they are useful.

I solved my problem. I'm enjoying WZ. as ever, with new maps and everything. thanks to the forum. While testing for Zarel, probe several versions, some worked and others did not. I gave all the information that he asked me in my limited knowledge. Version 2.2.3 - 2.2.2 are the only one that does not works perfectly in my computer.
2.2b1: works.
2.2b2: works.
2.2rc1: works.
2.2.1: works. .accept new maps.they work OK. :suprised: :suprised:
2.2.2: freezes. . accept new maps.they work OK
2.2.3: freezes. . accept new maps.they work OK
I am using 2.2.1.perfect.
I have the time and desire to help solve the problems in the versions that still fail, tell me how I help. Naturally help means to me, send report whit adequate means failure. .Easy task but it seems everything I am capable of.
Help to solve it would required to be born again

[-Kosh-]

if we look at the beginning of this, the quote ones and compare whith the normal problems report done by normal people. There are two worlds apart, look for a bridge of communication.
I'm sure many people are just playing Wz. Most of them without knowing how a game works, just play.
I read about Warzone 2100 publicity. Excellent Idea.
This forum it's about make Wz. better. most people here care about, not just play Wz. Try to exploit the problems posed by those who do not know, creating the tools. So they are useful.

I solved my problem. I'm enjoying WZ. as ever, with new maps and everything. thanks to the forum. While testing for Zarel, probe several versions, some worked and others did not. I gave all the information that he asked me in my limited knowledge. Version 2.2.3 - 2.2.2 are the only one that does not works perfectly in my computer.
2.2b1: works.
2.2b2: works.
2.2rc1: works.
2.2.1: works. .accept new maps.they work OK. :suprised: :suprised:
2.2.2: freezes. . accept new maps.they work OK
2.2.3: freezes. . accept new maps.they work OK
I am using 2.2.1.perfect.
I have the time and desire to help solve the problems in the versions that still fail, tell me how I help. Naturally help means to me, send report whit adequate means failure. .Easy task but it seems everything I am capable of.
Help to solve it would required to be born again

I still do not understand what you are trying to say.
Are you inferring that my diagnoses of the issue in my quote is incorrect?
You do not have vista right? Why are you posting in this thread?

From what I can understand from your posts wz freezes for you. Does that mean machine is locked up?
I did a check on trac and did not see any problems like you described.
I did not find on the forums any other mac person that has your issue(s) so it is specific to PPC macs correct?

Might I suggest you start a mac specific thread and make a trac ticket so other PPC mac users can get together and figure out what the problem is.
It might also help a great deal if you read this http://developer.wz2100.net/wiki/BugReporting