I checked again, this time with the fsport mod.ini that came with my fsport3_1.zip, but after changing fsport-mediavps to
fsportmvps, so that it reads:
[multimod]
primarylist = fsportmvps;
secondrylist = mediavps;
Using that in the Windows launcher works, but the result is different from what yal uses. The windows launcher interprets this as:
-mod fsportmvps,fsport,mediavps
I wrote my own xyz/mod.ini, which uses:
[multimod]
primarylist = abc,zzz;
secondarylist = def,ggg;
This results in
-mod abc,zzz,xyz,def,ggg
So the Windows launcher, which as far as I can see is the only authority so far on how the mod.ini file needs to be interpreted, puts the mods from "primarylist" at the beginning of the list, then adds the selected mod, and then adds the secondrylist mods. This is different from yal, which puts the selected mod first, then primarylist, then secondrylist. Maybe yal should change it's behaviour in this regard (and *maybe* the way mod.ini is to be interpretated should be standardized some way, e.g. in the Wiki, by someone or several someones who have the authority to do so). Well, anyway, it looks like I found the answers to all my questions, thanks a lot *g*