Thanks, BC.
With a large HDD in the Tb order, I agree it makes sense duplicating CFS2 as many times as how many war theatres one wishes to have. It will surely be my choice when I will be forced to retire my current pc. I guess tracking each theatre with separate installs is much simpler than the old, yet brilliant, Jean Bomber's method.
Each time I decide for a change in such architecture, I have to plan long and hard well in advance what I will be doing and which area of the CFS2 legacy files it will affect, least watching the entire sim going on me!
Over the years, I expanded those batches so much that they, not only change aircrafts and sceneries around, but switch ground/water textures where I have two CFS2\TEXTURE directories, one with PTO textures only and one with ETO, or rest of the world, textures only. Moreover, remove PTO files like the stock airbases when switching to the ETO/MTO theatres, change object, vehicle and weapon libraries according to the theatre, change theatre object textures, change ship types and even AI external sounds, as in Korea where I did not like hearing piston engine sounds around me when I was flying jets dogfighting other jets.
I also did a small test a while ago in renaming the executable CFS2.exe, like for ex.: CFS2_ETO.exe. It works normally with no problems whatsoever and that would be my choice with different dedicated single installs. From my jurassic programming days, I still fear conflicts among applications running with the same executable filename, as I witnessed the most incredible things happening over the years, which made be doubt several times the postulate: 'Computer science is an exact science'.
MR:
I will attach one of those batch files for you.
Cheers!
KH
Bookmarks