Win2k is not a supported operating system for these games, so if you're using win2k and are getting the access violation error right after the credits, there's nothing we can do at this time. The same problem has been reported by a few win2k users, for whom upgrading to XP SP2 is obviously not an option.
FIRESTORM WOW ERRORS ACCESS VIOLATION UPGRADE
If you don't want to upgrade to SP2, I'm afraid there isn't anything else we can suggest right now.
I"ll try it, and post results.įor people who have the error right after the credits, we found that upgrading to SP2 fixes the problem.
FIRESTORM WOW ERRORS ACCESS VIOLATION FULL
The 'large one' is the only one you need, but it never hurts to have more info!ġ) It'll be difficult/annoying to play with windbg if sam and max is running in full screen mode, hence that suggestion.Ģ) You may need to do 'show to desktop' in order to be able to see the windebug window while S&M is running - it seems to have 'stay on top' activated.Īctually, I suspect it's easier to get a drwatson dump instead via:īut I haven't verified that works well. IN the calls window, in the upper right corner, there is an icon that you can right click on, that lists the option 'copy stack to clipboard'.Ĭopy, and post to this thread, the three stack dumps. THe contents of the Calls (call stack) window will change for each thread. Knowing what the program is doing at the time of the access violation is a tremendous help in debugging.Ģ) Start Sam and max: set options to turn off full screen.ĥ) play the game until you hit the access violation box.Ħ) Go back to windbg, and do: Debug -> breakĨ) click on each thread in the processes and threads window. I am currently doing the following in order to gather additional info when my next access violation occurs. WARNING: Stack unwind information not available. I work in Tech support, so I know that printing just an access violation address isn't going to be a huge help.
The message is:Įrror: Access violation at 0x00000002 (tried to read from 0x00000002), program terminated. In fact, I know for a fact it's ave related - it just happened when I hit 'save'. Seems to happen shortly after an autosave. I'm getting a different access violation.
0 kommentar(er)
