History

It happens for me both when I start a listen server with that map or when I join a dedicated server running the map.

So it seems more a client issue to me, since the ded. server where it happened was running the mission with others (presumably non-beta clients) playing on it - only my client couldn't join unless I started CO without beta.

OTOH, I didn't test if a beta dedicated server would lock up too, trying to load the mission.

I had this problem too and tried to find the error source. The error source was the -exthreads game startup parameter. Once it was removed it did work. Iam on a dual core CPU so the exthread parameter was 0 then for me. If you have more then two cores the game does choose a exthreads value itself that is higher then 0. So try if the problem is solved for you with removing the exthreads parameter and/or setting it to 0 >> exThreads=0

exThreads has been introduced to OA with the beta patches right? Without the beta patch this parameter is not available so the mission works. It is a exThreads problem.

It holds after i click on continue on the map screen. All i get is then the receiving message. Alt + Tab doesnt work. CTRL + ALT + DEL works.ArmA 2\Expansion\beta\arma2oa.exe" -mod=Expansion\beta;Expansion\beta\Expansion -nosplash -exThreads=xxx

Damn, whondering what the error source is. What else could it be hmmm. We need to find the common denominator. I just post some other details of my system, maybe we find something together:- ATI 4850 - 512 MB- Windows 7 - 64 bit- Creative X-Fi (Soundcard)- Intel e8200 (Dual CPU)- no software running during gaming- Game and Operating System runs from SSD

I rather think it's the way how the game got installed or configured or something.

Mine is Retail (both parts) and was installed as ArmA2 only, patched throughe every patch ever appeared and then from 1.05 to 1.07 eventually, played it a while as such. Then I installed OA over it (as soon I got it) and patched it to 1.52, then the BETA patch(es).