I'm about to change my motherboard/cpu/memory and so will need to re-install Windows 7 (64), and of course FSX. I have some saved flights in FSX that I would like to keep and reinstall into the new FSX instance that I will create. I realize that I will need the relevant aircraft installed that are referenced in the saved flights. As well as saving the FSX folder in C:\Users\<name>\AppData\Roaming\Microsoft, which other files / folders should I back up? Some of the saved flights have specific weather configurations, I assumed those weather settings are also saved with the flights?In addition, I would like to save and transfer to my new FSX install the views in my EZCA application. How would I do that? And, to save and re-install my FSUIPC settings, I assume just saving FSUIPC.ini in the \FSX\Modules folder will do that.Final question- in prior reinstalls of FSX I have sometimes had issues with SimConnect not installing satisfactorily. The fix that I have used (came from Pete Dawson's site I believe) involves deleting the SimConnect folder after the re-install of the RTM version, then doing a "Repair", and repeated as many times as it takes to make SimConnect installed correctly ( I always notice when it's not when I try and use my GoFlight comm module). Is it possible to back anything up before re-installing to get around this routine and ensure that SimConnect works OK? Assuming that's possible, I realize that anything I back up now will be at the SP2 level, I'm not sure if that's a factor for add-ons or not- whether they look for the RTM SimConnect version, or just how that works).Thanks for any info. Finally, having been here at AVSIM since (about) their first day of operation (hard to remember that long ago), I would like to echo other people's comments about how great the user base and AVSIM staff are at making this hobby of our's a better experience, and wish everyone a Merry Christmas / happy holidays. (Are there any other users here that recall "The List", the predecessor of the AVSIM site? :) ).Thanks, Bruce.

I'm about to change my motherboard/cpu/memory and so will need to re-install Windows 7 (64), and of course FSX. I have some saved flights in FSX that I would like to keep and reinstall into the new FSX instance that I will create. I realize that I will need the relevant aircraft installed that are referenced in the saved flights. As well as saving the FSX folder in C:\Users\<name>\AppData\Roaming\Microsoft, which other files / folders should I back up? Some of the saved flights have specific weather configurations, I assumed those weather settings are also saved with the flights?In addition, I would like to save and transfer to my new FSX install the views in my EZCA application. How would I do that? And, to save and re-install my FSUIPC settings, I assume just saving FSUIPC.ini in the \FSX\Modules folder will do that.Final question- in prior reinstalls of FSX I have sometimes had issues with SimConnect not installing satisfactorily. The fix that I have used (came from Pete Dawson's site I believe) involves deleting the SimConnect folder after the re-install of the RTM version, then doing a "Repair", and repeated as many times as it takes to make SimConnect installed correctly ( I always notice when it's not when I try and use my GoFlight comm module). Is it possible to back anything up before re-installing to get around this routine and ensure that SimConnect works OK? Assuming that's possible, I realize that anything I back up now will be at the SP2 level, I'm not sure if that's a factor for add-ons or not- whether they look for the RTM SimConnect version, or just how that works).Thanks for any info. Finally, having been here at AVSIM since (about) their first day of operation (hard to remember that long ago), I would like to echo other people's comments about how great the user base and AVSIM staff are at making this hobby of our's a better experience, and wish everyone a Merry Christmas / happy holidays. (Are there any other users here that recall "The List", the predecessor of the AVSIM site? :) ).Thanks, Bruce.

What are you going to save from the FSX folder in C:\Users\<name>\AppData\Roaming\Microsoft?The only thing I would save is your FSX.cfg JUSTas a refernce for the tweaks, but when you install FSX agian let it build a new cfg then just copy the tweaks back after you have run a FSX. You never know, you may not need some of the tweaks on your new install. I'd run FSX first and see how it is and tweak from there.For EZdok, you can run the sim, select the plane that you want to save the settings for, then open a flight on the ground somewhere, open the EZdok Studio from the drop down and export the camera for the plane you want to save the settings for. The when you reinstall, you can reimport the camera you exported for the same plane. Works well once you have it set up the way you want and is a lot easier that writting down all the settings for each plane.For FSUIPC, I would assume like you said that you could just save the .ini file.I've never had to do a reinstall yet of FSX, but if I did I would be sure to make a backup of any or all textures for sceneries, AI, or user aircraft that you may have spent time mip mapping. Also depending on what type of AI you are using, you may want to backup the traffic.bgls and aircraft folders for the said traffic if you have made any custom stuff or any alterations to any of your premade traffic.bgls.Aside from that, I wouldn't bother backing up any thing you installed that requires an running an installer to install to FSX since some of them write things to your registry. Trying to back up and a/c or something that has written to your registry probably wont work properly if you just back up it folder contents then drop it back into your new install. However, saving any custom mip mapping you may have done is ok, once you run the installer for that addon, you can then just copy and paste your mipped textures back in.

What are you going to save from the FSX folder in C:\Users\<name>\AppData\Roaming\Microsoft?The only thing I would save is your FSX.cfg JUSTas a refernce for the tweaks, but when you install FSX agian let it build a new cfg then just copy the tweaks back after you have run a FSX. You never know, you may not need some of the tweaks on your new install. I'd run FSX first and see how it is and tweak from there.For EZdok, you can run the sim, select the plane that you want to save the settings for, then open a flight on the ground somewhere, open the EZdok Studio from the drop down and export the camera for the plane you want to save the settings for. The when you reinstall, you can reimport the camera you exported for the same plane. Works well once you have it set up the way you want and is a lot easier that writting down all the settings for each plane.For FSUIPC, I would assume like you said that you could just save the .ini file.I've never had to do a reinstall yet of FSX, but if I did I would be sure to make a backup of any or all textures for sceneries, AI, or user aircraft that you may have spent time mip mapping. Also depending on what type of AI you are using, you may want to backup the traffic.bgls and aircraft folders for the said traffic if you have made any custom stuff or any alterations to any of your premade traffic.bgls.Aside from that, I wouldn't bother backing up any thing you installed that requires an running an installer to install to FSX since some of them write things to your registry. Trying to back up and a/c or something that has written to your registry probably wont work properly if you just back up it folder contents then drop it back into your new install. However, saving any custom mip mapping you may have done is ok, once you run the installer for that addon, you can then just copy and paste your mipped textures back in.

Thanks for the reply."What are you going to save from the FSX folder in C:\Users\<name>\AppData\Roaming\Microsoft?"As well as FSX.CFG, I wondered if saving the file EXE.XML might help with the SimConnect issue that I referred to, although I would be surprised if it did help- but at least I would have all of those files in case I needed them. I also assumed that the saved flights might be in that folder too, although I can't see them (assume they are .FLT files?).Thanks for the EZDoc info. Much appreciated. Bruce.

On the EZdok question, I opened FSX to double check.Once you have a flight going in the a/c you want save, go to windowed mode, then from the drop down select Ezdok camera addon/Show studio. Then in the studio go to file/export current camera and save it. Repeat for all the a/c you want to save.

On the EZdok question, I opened FSX to double check.Once you have a flight going in the a/c you want save, go to windowed mode, then from the drop down select Ezdok camera addon/Show studio. Then in the studio go to file/export current camera and save it. Repeat for all the a/c you want to save.

Thanks again. Bruce.

As well as FSX.CFG, I wondered if saving the file EXE.XML might help with the SimConnect issue that I referred to, although I would be surprised if it did help- but at least I would have all of those files incase I needed. I also assumed that the saved flights might be in that folder too, although I can't see them (assume they ate .FLT files?).

I would only save the EXE.xml and DLL.xml as a refernce but not to re-use.As far as the simconnect issue, you may not have any problem on the reinstall. Just follow NickN's install guide over on Simforums.com. There are three differnt simconnects. The only problem I ever had was when I got UT2 their product required an updated version of simconnect that I didn't have when I did the base install, then SP1, then SP2. You can always reinstall the newest one over it if you have a problem. Also I can provide a link for the simconnect issue I and others has and how to fix it should the issue arise for you in the next install. If I recall right, there was an update to the original SP2 simconnect that I downloaded from the MS site. I still have the lastest one if you end up needing it

.......... Also I can provide a link for the simconnect issue I and others has and how to fix it should the issue arise for you in the next install. If I recall right, there was an update to the original SP2 simconnect that I downloaded from the MS site. I still have the lastest one if you end up needing itForgot to mention that you can find the flights in the FSX root folder under flights and the WX files in My Docs/Flight Simulator X files.

Thanks, some great info you have! Thanks for the info on the .FLT and WX files. A link to the SimConnect issue would be great, no hurry though, just when you have some time.Thanks again, Bruce.

Thanks, some great info you have! Thanks for the info on the .FLT and WX files. A link to the SimConnect issue would be great, no hurry though, just when you have some time.Thanks again, Bruce.

No problem Bruce.Looking back on the flights you saved, it looks like they reside in the My Docs/Flight Sim X files. I dont have many I have saved, but the ones I did have a .wx, .flt, and .FSSAVE all associated to each one of them. The ones in the FSX root Flights folder looks to be ones from MS. So you will want to back up the ones in My Docs/Flight Sim X files, rahter than the roots FSX/flights folder.

Thanks- I see those files in the path you mentioned. This is excellent information, I really appreciate your help.Bruce.

Thanks- I see those files in the path you mentioned. This is excellent information, I really appreciate your help.Bruce.

On Win XP you can check your versions by going to C:Windows/WinSxS, then scroll down to the folders I put the red square around and open each one and right click on the properties of each simconnect file to see what versions you have. There should be 3 different simconnect folders like in the screen shot below.The versions simconnect I have installed, which I believe are the most up to date versions since I had to update one of them with a new simconnect.msi are:10.0.61637.010.0.61355.010.0.60905.0I'm not sure if Win 7 64 has the same file structure, but at least you can check to see what versions you have now on your current rig and will know if you already have the correct ones installed as it stands now.