For those with problems installing 1.05

[AiRec1 0]

I'm running Vista32 with following spec

C2D 6300 1.86@3.06OC

2GB Ram

Nvidia 8800GTS 320MB

3 x Hard drives

Since the patch came out I have had no end of problems trying to get 1.04(505 UK) to accept the 1.05 patch, errors everywhere on upgrade.

So using one of my other drives I thought I would run both OS, switching boot drive at boot menu when I want to play games.

Well re-install XP and the game last night and got the same errors, I had been installing to drive:\ArmA.

By midnight I was truly hacked off and ended up just installing 1.04 and using that, even tried to jump onto some servers, but most were 1.05.

This morning thought I would try some things suggested on the BI forum, so installed it to default install path on my e:\ drive, set the Temp Dir for windows to c:\temp.

Then lastly removed any overclocking on my machine(processor), and guess what the patch installed perfectly.

After the update switched my OC back on and back to normal, games runs OK

I had a quick test on the first SP mission, and with everything set to high/V high, and AA off, the frame rate seems good.

There is still the Fog issue with the 8800 GF cards, and some AI balancing needed(they are far too acurate when shooting at you eg sniper in cover prone, and 2-3 shoot at you and your dead).

I'm just glad to have got it working and hope this helps some of the others do the same, I'm still doughtful as to the reason for BI using the studip checker system in the patch, there is no need, all we need is an extractor that copies the updated files to the installed game directory as I have pointed out before on this board.

Ray

[troop 0]

Arma (especially patching it) is very (very) sensible to

overclocking/too sharp RAM-settings.

While it might run well once installed, you never know,

if there is not some lurking corruption of files beneath, which

only would show up when patching or specific situtations.

Btw, with OFP its the same story. Sooo, very good

file checking routine from BIS side! imho.

Many other games wouldnt tell you a peep, if file corruption

occurs (o/c-ed) and just bomb out with BSOD.

Hard to find out in any case.

Also that dreaded 'no spaces' in path installer problem is

around for an very long time. Even more annoying, that

one Windows installation could have it and another works

perfectly fine with the default (Temp) pathes. Thats BS.

Since I have had the same problems way back, one of the

first things I do is to change those pathes even before any

Win updates. *Any* (installer; especially older ones)

problems related to that vanished right away 'forever'

Well, until next fresh install, that is.