I quoted the what-appears-to-be-somewhat-confusing bit below.
In my installation (a standard, FSX-SP2 installation - no FSX-Steam - no nutin; ), The repair option was present. I suspect is also was for the OP if this thread.
Now, Robert above doesn't mention anything about uninstalling the 777 preceding the upgraded install. The fact that he wants you to run the ops center to 'capture' currently installed liveries kind of implies (to me anyways) that he kind of wants you to keep the 777 installed. I'm pretty sure specific user's liveries and options would be lost from the Ops Center if the 777 was uninstalled.
The language around the "update/repair" is a little vague. Granted, when you run the new installer, you are (typically) presented with two options. Uninstall, or repair. There is no "update" prompt or action. But Robert only states the installer may prompt you that cannot repair, then you have to uninstall - as it's an action only required in that case. Users seeing the cannot repair I suspect are running an even older version of the 777, or as in your case - have two FSX installs and the respective PMDG registry entries.
So my understanding/process was:
- Download new installer from PMDG eCommerce
- During download, ran Ops Center (Noted message that this update to 777 was available - but didn't action anything through Ops Center).
-Closed Ops Center (and didn't have FSX or anything like that running of course)
- Ran new installer (200LRF only - don't have -300)
- Wasprompted with Uninstall or Repair
- Selected Repair
- InstallWizard appeared to do a pretty thorough install of 777 update (For me, it took just as long as I recall the initial install did - appeared to reinstall all the gauge and dll magic...and those pesky large-chunky .DEM files).
- Install complete (or should I say 'Repair') - Installer and stuff closed.
- Ran Ops Center - Was prompted to repair liveries and such - completed that. Version info checked serviceable as current.
- Went on me merry way.
- Re-installed current NavData as installer appeared to install default NavData.
I agree with you regarding an installer providing an "update" kind of message typically - but I'm pretty sure the InstallShield installer PMDG currently uses doesn't support that.
I hope one can understand what I'm trying to get at here. I know my explanation is perhaps as head-scratching as Robert's post . The wonders of the written word - so powerful - but so limiting!
I just don't want PMDG to be fighting all this tickets/support regarding existing memory issues when they could nip-it-in-the-bud with a true, full re-install.