CM: Battles in Normandy Patched to 1.11

[bob48]

The original CM3 had some Tunisian and Sicily scenario's which were pretty good.

[Staggerwing]

I was hoping more for entrenched Aussies, Semoventas, and helmets with black feathers, that sort of thing.

[Zulu1966]

De aware that the patch may create a subfolder -Battlefront/Combat Mission Battles for Normandy/Combat Mission Battles for Normandy- that kills the install. Just delete the second folder in the path.

I must be lucky :D. For once I didn't have Norton 360 screw up my install and delete the main .exe as it did with CMFI v1.01 (and that was a pain to fix - thanks Symantec! >:().

How did you fix it? I just patched CMFI to 1.01 and had my exe deleted as well. I uninstalled the game this morning and was going to try reinstalling at some point soon.

I did an explanation on the problem and how to get around it and sent it to Battlefront Support. I think there is a link on the website somewhere for it. But as it's you Ubercat :), I'll save you time and cut and paste from the note I have on my PC, viz:

**WARNING** Norton 360 notes for Battlefront CNBN: Commonwealth Bundle

Here is the precise workaround that your
customers need to use to avoid Norton deleting the CMBN Commonwealth files
at download and subsequently at installation. I've tested it through bitter
experience and this solution works:

If your customer has Norton installed they must first set up a download
folder for the game and an install folder for when the bundle has
downloaded.

Then go to the Norton 360 menu screen and click:

1.    Settings
2.    Antivirus
3.    Scans and Risks
4.    Under "Items to exclude from scans" click configure
5.        Click Add and then browse the install and apply it
            Do the same for the download folder
6.    Under "Items to exclude from Auto-Protect and SONAR Detection" click
        configure
          Click Add and then browse the install and apply it
            Do the same for the download folder

That's it. You can now download and install.

Ubercat, I hope that solves the problem for the download. I should add that with the CMFI experience I had, I needed to re-install to get the .exe file back, then go through the same process as above for the Combat Mission game folder, since the .exe was still being deleted when I applied the patch. In the end I copied the .exe elsewhere whilst I tried to fathom this out. I know how frustrating you'll have found this. 8)

BTW I'd hasten to add that this is a Norton 360 issue and not a Battlefront one. I complained to Symantec about this on the first occasion I had the problem. I gather that Martin at Battlefront's support did so as well. Battlefront.com are "approved" as a safe site by Symantec, yet gamers have this problem due to the "reputation" program Norton runs. It clearly doesn't make much distinction between good and bad. To help the Battlefront game community, I'd suggest you complain to Symantec in the hope that if they get enough complaints, then they might actually listen.

You can also just turn off the auto protect function for as long as you take to do it. This is what deletes the file. The reputation feature of their system has cause me more headaches than it solved. I would be interested to know just how many people have to log a use of the  file for it to be safe. the system only acts on a file at the time its being written to disk not after.

[Bison]

All you need to do is go into norton latest scans look for quaritine or something like that files and then restore.  Done and done.

[Zulu1966]

All you need to do is go into norton latest scans look for quaritine or something like that files and then restore.  Done and done.

Only sometimes the Norton rubbish doesnt send it to quarantine at all - it deletes it completely so you cant find it. the explanation being that given the system has no idea what the file is the safest course for it is to completely remove all trace of the file. It did this with the commonwealth file on the 1.10 update - had to reinstall the whole thing.

[Bison]

It's diffinately possible but I know is that is all it took to recover the .exe files.  I also had to do the same thing with MS essentials. 

[Zulu1966]

It's diffinately possible but I know is that is all it took to recover the .exe files.  I also had to do the same thing with MS essentials.

Yeah - nortn seems to have a mind of its own. Frankly I hate it but have a three year subscription. I am sure it also slows down my browsing.

[MengJiao]

De aware that the patch may create a subfolder -Battlefront/Combat Mission Battles for Normandy/Combat Mission Battles for Normandy- that kills the install. Just delete the second folder in the path.

I got it and it all worked and I actually saw some of the fixes in action: better models, troops properly aligned with slopes.

British Battalion HQ tanks seem pretty lucky.  I had a Churchill Battalion HQ  tank with a 75mm gun knock out a Jadgpanzer with a quick flank shot and then get the Marder in one test I tried.  At least that showed that 3 models were improved visually.

[Boggit]

Thanks!

So for the install folder, I should probably just create the same folder that the game itself would be creating to install itself to. And then during the install, Norton would exclude that folder from skullduggery.

I have CMFI on disk, so in that case I'm guessing the D/L folder would just be for the patch?

I'm in the same situation. I'd make sure that you do this for the CM/CMFI/ folder. D/L to the folder an execute it from there. If Like me you store patches for reuse - make sure that when you store the patch you exclude it from scans etc to avoid inadvertently having it delete during a general virus scan.

[Boggit]

All you need to do is go into norton latest scans look for quaritine or something like that files and then restore.  Done and done.

Only sometimes the Norton rubbish doesnt send it to quarantine at all - it deletes it completely so you cant find it. the explanation being that given the system has no idea what the file is the safest course for it is to completely remove all trace of the file. It did this with the commonwealth file on the 1.10 update - had to reinstall the whole thing.

This happened to me first time round, before I worked out a fix for the thing. Bloody annoying! >:(