New patch restarting my computer...

[pipes100]

Since I did a fresh install of my "Soldout" Worms and then updated to .28, my computer has restarted TWICE after quiting out of a Deathmatch. I select "quit", hear a "fatal error" beep and then the next thing I see is DOS. I'd say its about 10% repro for me.

And another time, I quit and it went back to the Deathmatch lobby area, but it had forgoten the match I just won before this one. So I had to redo that match to get back to the one that I quit out of. To counter this, I exit the game after every round I win so it gets saved for sure and then reopen to play next round in case I need to quit it (pain in the ass).

So, quitting out of Deathmatch is definetly not acting perfect for me. However, the game used to crash to my desktop alot after quits or completing a match and that has'nt happened once, so that's good. So hopefully the code involved with "quitting" can be looked at for the next beta.

Would changing the Windows "compatability mode" to Windows 2000 or 98 be advised? Thanks.

Here's my specs:
AMD Athlon64 3500+ 2.2ghz.
Asus A8N-SLI
1 Gig Ram
GeForce 6800 256mb
Win XP Pro SP2
Madcatz Microcon 360 controller

[CyberShadow]

Computer restarts are a sign of hardware or driver failure. Try upgrading your drivers, and disabling unnecessary devices.

The changes since the last beta may not be directly related to our changes to the game's code - this version is compiled with a newer version of Visual Studio, so it might be caused by the runtime as well.

[pipes100]

Computer restarts are a sign of hardware or driver failure. Try upgrading your drivers, and disabling unnecessary devices.
Well, I'm using a 4 month old computer, so its probably not the hardware.

I'm also using the official 93.71 drivers. If it happens again, I'll try grabbing the next official driver or wait for a good hundred series driver.

The changes since the last beta may not be directly related to our changes to the game's code - this version is compiled with a newer version of Visual Studio, so it might be caused by the runtime as well.
I do have the MSVS2005 SP1 runtimes as of like April. I'll see if there's some newer ones.

But again, do you recommend setting the "Compatability mode" to 2000 or 98/ME or stick with XP?

[CyberShadow]

The W:A executable is statically linked to the runtime, and it's also using VS2005SP1 libraries.

I can't make any recommendations on the compatibility settings, but it won't hurt to try :)