Trouble with additional ETO 1.5 install ( WIN10)

[mongoose]

1. Installed ETO 1.5 on C: drive and works fine.

2. Batch files (startup, ETOGLswapper, mucusicswapper) changed to CD "C:\Program Files (x86)\Microsoft Games\CFS3 ETO Expansion\...." wherever needed

3. Copied all files (after setting to era 1 and spawns 1) tp new C: folder "Combat Flight ETO TOWplus"

4. Batch files (startup, ETOGLswapper, mucusicswapper) changed to CD "C:\Program Files (x86)\Microsoft Games\Combat Flight ETO TOWplus\...." wherever needed

5. ran MultiCFS3 and changed name to Combat Flight ETO TOWplus

6. Upon starting always goes to era 1 whatever era I select.

Any ideas??

 

[italflyer]

Just a quick shot: try not to install to the program-folder, but somewhere else, like C:\games\eto (etc.) or even on another drive than C:.

 

[mongoose]

Just a quick shot: try not to install to the program-folder, but somewhere else, like C:\games\eto (etc.) or even on another drive than C:.

I'll try outside prog x86 bu the reason it's in C: is because that's an SSD. I already have lots of installs in D:

 

[mongoose]

Well changing it to just C:\ seems to work eventually although had to do a few odd things to get it going.
However would sort of like to know why it won't work in C:\Program Files (x86)\Microsoft Games\????

 

[hairyspin]

Because MS have upped the security model first introduced with Vista and its UAC. Now Program Files and Program Files (x86) are heavily protected by the OS and the batch files run by ETO, especially to change era, are blocked by Win 10 from altering any files. You don't get any warning when the block operates, they just don't work.

 

[mongoose]

Interesting! Even if run in SP3 mode?

 

[Daiwilletti]

it's got to the stage where I run my Win 10 dedicated CFS3 computer with the wireless adapter unplugged. I then disable Windows Defender, and turn off User Account Control completely. I also run CFS3 on the D SSD drive, rather than the C OS drive.

I also have an unproven theory that some dlls are being blocked from doing their jobs (principally doing all the probabalistic die rolls required) between campaign missions. This means I have run an incredibly long 1944.xml campaign in ETO 1.50. Much longer than a stock campaign used to take. The only good thing about it is that my campaign progress has eerily matched progress of the actual ETO theatre - invading Normandy and taking almost a year to get across the German border.

Thanks a bunch MS for being such a pain.......