TOAW, France 1940

[Paddybhoy]

I just got the game, and it keeps on crashing about 6 turns into the France 1940 scenario, I tried the patch but I don't think its wrking

I'm using windows XP and have tried most of the compatibility options

[billslim0]

hi - where did you get the patch? if you try the 1.04 patch from the site below, it ought to work

good luck!

http://www.warfarehq.com/index.php?page=toaw/toaw_news.php

[Ben Turner]

At what point in the game turn does it crash? Is there an error message or does the program just end? If you can run the game at all then it's unlikely to be an operating system issue.

[Mantis]

Only one compat option works - Win 2000 compat mode.

[Ben Turner]

Only one compat option works - Win 2000 compat mode.

It's murky. I run Windows XP- and I don't use a compatability option for TOAW at all.

Like I said, if the game runs at all, it's unlikely to be an Operating System problem.

[Mantis]

My game runs without it, but not well. Menu/Report windows only partially display, and sometimes disappear completely, but are still 'there'; you must press enter to close them. Composition windows only partially display, and the combat planner will show large areas of map terrain instead of the window in certain areas.

[Paddybhoy]

Well I get the standard 'an error has been detected report' and when I look at the details i get

Error signature: opart.exe AppVer:0.0.0.0 NodName: kernel32.dll
Modver:5.1.2600.1106 Offser:0001f14f

Also it usually happens in the northern section of the map usually (but not always) when i'm interfacing with dutch, french and belgium units (note this is a rolling problem that has occured since turn 4, I'm at turn 8 the now)

[Ben Turner]

Well I get the standard 'an error has been detected report' and when I look at the details i get

Error signature: opart.exe AppVer:0.0.0.0 NodName: kernel32.dll
Modver:5.1.2600.1106 Offser:0001f14f

Also it usually happens in the northern section of the map usually (but not always) when i'm interfacing with dutch, french and belgium units (note this is a rolling problem that has occured since turn 4, I'm at turn 8 the now)

This doesn't sound like a normal running problem. You've tried the compatability mode suggested by Mantis? The only other thing I can suggest is try other scenarios to see if the problem reccurs.

[General Staff]

I just tried opening France 40 in ACOW with OPART300 (the Huge Map version of the game). It wouldn't open. Then I tried opening with OPART (the little map version of the game)- that worked. Can anybody duplicate this problem and solution?

[General Staff]

Furthermore when you open up the Editor in the little map version of the game (OPART) and save the scenario (File->Save As), it will then open in OPART300 (the huge map version of the game).

You can then open the editor in the huge map version, load the scenario, save it, and you have a working OPART300 (huge map version) France 40 scenario. Does this solve your issue?

[nemo]

I just tried opening France 40 in ACOW with OPART300 (the Huge Map version of the game). It wouldn't open. Then I tried opening with OPART (the little map version of the game)- that worked. Can anybody duplicate this problem and solution?Works fine here with both versions of ACOW on an XP Pro system.

[Mantis]

Same here. Opened it without difficulty on both exe's.

[Dan Neely]

What error did you get? Ihave trouble opening scenarios (esp larger ones) in acow if I have a number of other apps running. At the largest end I often need to kill my browser and email to avoid running out of 'resources' during the load.

[Mantis]

Yeah, CoW can be a resource hog.

[Ben Turner]

What error did you get? Ihave trouble opening scenarios (esp larger ones) in acow if I have a number of other apps running. At the largest end I often need to kill my browser and email to avoid running out of 'resources' during the load.

You might want to increase your virtual memory if you can.

Still. This shouldn't cause the problem this guy's referring to. For a start, France '40's just not that large a scenario. Further, such an error would just pop up saying "Not enough Virtual memory" or whatever and close the program. Nothing about kernel32.dll.

[Dan Neely]

You might want to increase your virtual memory if you can.

Still. This shouldn't cause the problem this guy's referring to. For a start, France '40's just not that large a scenario. Further, such an error would just pop up saying "Not enough Virtual memory" or whatever and close the program. Nothing about kernel32.dll.

I'm 99% sure it's not a memory issue. I've had it happen when I had over a hundred megs of free physical memory in addition to a large page file. Adding 256MB of physical ram didn't help either.

edit: while 'not enough resources' could be a generic error for running out of several things, my guess would be that acow tries to grab too many "GDI resources". THis would fit with failures appearing to be ram invariant, and the paint failures I've mentioned in other other thread (GDI is windows graphics subsystem and the stock of "resources" available for applications using it is strictly limited).

This is getting farther afield into speculation, but if toaw uses some sort of smart pointer system instead of manually disposing of the resources too infrequent garbage collects could be the source of the problem.

[Ben Turner]

This is getting farther afield into speculation, but if toaw uses some sort of smart pointer system instead of manually disposing of the resources too infrequent garbage collects could be the source of the problem.

This sounds familiar. I've certainly heard of TOAW causing serious memory leaks, leaving a great deal of memory unavailable even after the program's been closed.

[General Staff]

I'm 99% sure it's not a memory issue. I've had it happen when I had over a hundred megs of free physical memory in addition to a large page file. Adding 256MB of physical ram didn't help either.Agreed- not a memory issue, as long as you've got a reasonable amount to start with (I think I found 384Mb was the limit to get it to work). My system still crashes when trying to dump 'HUGE' (DNO-type) scenarios, and I think that's a bug with TOAW trying to access memory it perhaps shouldn't. At one point I tracked memory usage during a crash and found that at the point of failure there was plenty of memory available.

We've also covered a lot of previously:
http://www.strategyzoneonline.com/forums/showthread.php?t=2325&highlight=memory
http://www.strategyzoneonline.com/forums/showthread.php?t=743&highlight=memory