I could have saved those settings using the "MPU2016" program but did not.
However, as I had not done anything to change the ini settings I was able to save them using the DirSetPicker:
I selected the "NewETO(Ray)" folder, named the file "EderTest" and clicked "Save current ini file".
To test I loaded another one "Trieste Test.txt" which modified my ini, but then reselected "EderTest".
When I ran a multiplayer game I got the settings I made in the first post.
I will not go into detail about how this works, but there are two key folders.
The first is "Theatres" from which the "MPU2016" program gets its data.
There are subfolders in it for the theatres, with planeset folders in them.
These planset folders need two files, the appropriate "frntline.dat" file , and the "FMDir.set" file which is read to get the aircraft names.
The second folder is "MPData" where files get saved by both the "MPU2016" program and the DirSetPicker.
The DirSetPicker loads them from that folder.
The "MPData" folder has subfolders for the various scenarios, and there is a useful "ZERO" folder with a "ZeroSettings.txt" file in it:
This can be used if the user's existing settings seem to be causing problems in a multiplayer game. The critical eight values in the player's "eaw.ini" file are all set to =0.
Doing this manually fixed a problem Shogun had online last night, but it is more easily done with a couple of mouseclicks in the DSP