Hi all,After you have installed the update BACKUP YOUR MODULES FOLDER!A few days ago I congratulated myself on successfully updating FS to version 9.1 :) Today I installed a 3rd party a/c and quickly discovered I would have to go through the process again :(The file in question on this occasion is 'Traffic.dll'. Like many of you good folks here, my usual practice is to unzip the archive to a temporary folder and then transfer the files to FS9 by hand. This becomes automatic after a while and so today I was caught out. Despite overwrite warnings appearing on screen I sailed on regardless and transferred the two .dll files into the Modules folder. THEN, realising I had been a bit too hasty, I decided to check and found that Traffic.dll had been replaced with the previous FS9 version...ugh!Please be aware that the default FS9 Module files are allversion 9.0.0.30612Following the 9.1 update installation these all becomeversion 9.1.0.40901Traffic.dll had, on this occasion, been overwritten and had reverted back to version 9.0.0.30612Now, on this occasion, the mistake could have been avoided if I had been paying a little more attention. But, what of the automated installers? Some you can control, others you can't.In a previous post someone recommended changing all the .dll files following the 9.1 update to 'Read Only' to prevent future overwriting. This may be an effective way of avoiding having to uninstall and then reinstall the update to restore the status quo. However, MS have not set up the files to be 'Read Only' and I can only speculate as to why they may have done so. Perhaps instead it would be better to make copies of all the files in the Modules folder immediately post update and restore them by hand as and when it proves to be necessary.One good thing came out of this experience. I was able to demonstrate that the FS9 Update uninstaller worked perfectly and the reinstallation of the update took about 3min. 45secs. Remember to delete the Backup folder in FS9 root folder AFTER running the uninstaller 'FS9UpdateUninstall.exe' and BEFORE running 'fs91upd.exe' again.Mike

Good advice...One pet peeve of mine are add-on packages including default gauges, dll's, sounds, effects, etc.... Not only does it risk newer files being overwritten by older ones, it also inflates package sizes by quite a bit. -John

That

Hi Mike,Done. Thanks for the reminder!JackD

Great advice...thank you MikeI would not have known of this issue. I will watch my installations from now on!

I wonder if it would be a good idea to temporarily change the name of the FS9 folder before using any exe install package? That way the install should make a new folder called FS9, which of course would only contain the installed files. Afterwards the files can be placed wherever considered necessary, then delete the new FS9 folder and rename the original back. I think this is based on someone else's original idea but I thought it worth mentioning.

Good tip. Thanks.

>I wonder if it would be a good idea to temporarily change the>name of the FS9 folder before using any exe install package?I have never seen any installer for an add-on that wouldn't allow you to simply aim the durn thing to another folder, such as C:Install TempThat's a whole lot simpler, and a lot less effort.

Hi Bill, "I have never seen any installer for an add-on that wouldn't allow you to simply aim the durn thing to another folder, such as C:Install Temp" I hope you're right Bill, and it would make sense for addons that need to be installed to a FS folder that is not where it normally should be, but I wrote my post in response to the original poster's comment that some installers can be controlled and others not. I couldn't help thinking I had seen at least one that acted as the latter, but I'm not totally sure now. At least if I do ever see another I will know what to do.

Thanks for the heads up, I found that I had already over-written that particular file...

Thanks for advice. I found that "TrafficInfo.dll" in the modules folder has not updated from 9.0.0.30612 to 9.1.0.40901. Have uninstalled and deleted backup, reinstalled but still this file remains 9.0.0.30612.Is this correct? If not how do i fix?Thanks for any advice

"Remember to delete the Backup folder in FS9 root folder AFTER running the uninstaller 'FS9UpdateUninstall.exe' and BEFORE running 'fs91upd.exe' again."I don't remember if I did this or not. What would be the effect if I did not?Thanks,Robbie

Maybe there's an even more important lesson to be learned here. One should always do a complete back up before AND after any major upgrade or version change. As soon as I finished the FS9.1 upgrade and verified it was operational, I saved the entire FS9 installation to DVD.Good backup practices are an essential universal precaution against these sorts of unhappy surprises, in addition to protection in case of the dreaded "why is my HDD making that funny noise" event...RegardsBob ScottATP IMEL Gulfstream II-III-IV-V L-300Washington, DC

I noticed that my TrafficInfo.dll was not a 9.1 also. This appears normal. No need to update?-T

Why would you delete the Backup folder in FS9 root folder AFTER running the uninstaller 'FS9UpdateUninstall.exe' and BEFORE running 'fs91upd.exe' again?Thanks,Robbie