Simple solution...rename you boxed fsx.exe "fsx_box.exe" and rename your FSX.cfg "fsx_box.cfg"

 

and then point nVidea Inspector to that exe. I have seversl"fsx_.exe files on my

 

system fir various configurations/environmenets as well as the appropriately named cfg files.

 

I also rely heavily on FSUIPC4 and have 'like named' FSUIPC4_.ini files plus the .key files.

Thanks Paul for these tips. I'll try them when I get back to my FSX computer in a few days. But one question: As I understand you, you are saying that, if I renamed FSX.exe to FSX_01.exe, and renamed its corresponding fsx.cfg file (in the proper folder, approximately, from memory, c:\users\[name]\appdata\roaming\fsx) to fsx_01.cfg, that 1) clicking on fsx_01.exe would start FSX, and that 2) fsx_01.cfg would still be the .cfg file that fsx relies upon?

 

Thanks,

Mike

Thanks Paul for these tips. I'll try them when I get back to my FSX computer in a few days. But one question: As I understand you, you are saying that, if I renamed FSX.exe to FSX_01.exe, and renamed its corresponding fsx.cfg file (in the proper folder, approximately, from memory, c:\users\[name]\appdata\roaming\fsx) to fsx_01.cfg, that 1) clicking on fsx_01.exe would start FSX, and that 2) fsx_01.cfg would still be the .cfg file that fsx relies upon?

 

Thanks,

Mike

 

Correct. As long as you make a copy of the CFG file and then rename it to the same

name you use for the exe, then everything will remain the same. I recommend that you

keep the original fsx.exe and just create a copy and rename the copy. You could also just

change the exe extention to exe.save or some such.. When you start the renamed exe it

will look for a cfg of the same name. If it finds it, that will be used.

Otherwise it will create a new cfg witj the new name.

 

 Paul