Jump to content
The simFlight Network Forums
Sign in to follow this  
abz

upgrading 8.3 to 8.4 question

Recommended Posts

I just installed 8.3. Used it several times and then downloaded the upgrade to 8.4. I took the two 8.4 exe files (FSC84.exe and FSCDbManager84.exe )and placed them in the FSC folder. Initially I removed the two previous 8.3 exe files. When I opened FSC with the new FSC84.exe, it first created another FSC83.exe and FSCDbManager83.exe files. I now have both 83.exe and 84.exe files in my FSC folder. Are there supposed to be 2 of each there after upgrading to 8.4? Was I supposed to leave the 83.exe files there from the beginning??

I also noticed there are several duplicated files in the FSC folder, with ".old" next to them. Are these supposed to be there?

Just want to make sure that everything is correct Thanks, Al

Share this post


Link to post
Share on other sites

Hi Al,

there is no reason to delete the older version.

Just following the instruction for the update/patch and don't forget to create to new Links for the

Databasemanager and FSCommander on your desktop to make sure that you run the current, new version.

Never delete the *.old files, there are a part of the program.Volker

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.