![]() I just recently installed FSX and Acceleration. ![]() ![]() If you are getting error messages, there is a fix. NET 4.7 manual install and runs perfectly. I choose the manual install as there appears to be a problem with Rikoooo's installer.ĪICarriers2 is also a. Search for 'Orion Special Operations' if you are interested.Ĥ0 aircraft in different liveries. Rikoooo produce a superb Bombardier free add-on. I found an F-18 Super Hornet Blue Angel for use with AICarriers2 so it should make it a worthwhile simulator for a novice. I will just have to be content with installing some add-on aircraft. I have installed MS FSW Gold Edition but cannot install the Acceleration update as Microsoft has withdrawn the on-line activation process. But then I have installed two 250GB Samsung EVO SSDs to replace the 2 old 2TB 5,200 rev/min Seagate HDDs and upgraded the AMD 2GB video card to a Nvidia 1050Ti 4GB which is all that the motherboard will handle. There was no additional scenery involved just the basic v4.2 installation.Īs a result my Windows 7 computer is now running like new after compressing the registry some 11%. This approach can solve a lot of hard deployment problems - or prevent them from ever existing.The total number of Prepar3D v4.2 registry keys removed was 29,172. With all that being said, I want to ask if these registry settings are in HKCU or in HKLM? It is generally not recommended to write settings to HKCU form MSI setups - you should rather populate HKCU when your application is first launched. To get ahead of myself: if you can change the location of the registry key (For example from HKLM\Software\Company\MyProduct to HKLM\Software\Company\NewProduct - which is usually not possible) and then also set a new component GUID for it, then you should be "de-coupled" from the sins of the past and your new MSI files should share the component properly. The problem is only solved when both your setups "know" that the component is shared and its registry keys should be left alone.īefore I elaborate this, are these MSI file live? As in published in the wild, or are you still in development? There is an answer here that might help if you take the time to read it thoroughly (I think I recommend this - please give it a once-over):Ĭhange my component GUID in wix? (please do read this answer, see if it still makes sense).Īnd now a further complication: having deployed your old MSI files "in the wild" means that setting a stable component GUID from now on will not necessarily help to sort out the problem since your old MSI being uninstalled as you install your new MSI still thinks it "owns" the registry key when it is being uninstalled - and hence will delete it. Understanding component reference counting is key to understanding MSI. Once it reaches 0 when the second product is uninstalled, it will be uninstalled (unless it is marked as a permanent component). When one product is uninstalled the reference count will be reduced to 1 and the component will hence not be uninstalled. Once the same component GUID is used in both MSI file, the reference count for it will be 2 when both products are installed. Essentially this would entail putting a single component in a WiX source file that is then included by both setups, something like this (using the preprocessor feature in WiX): How to include wxi file into wxs?. You should also be able to use WiX include files - though I have to admit that I have never taken the time to actually try it. MSI's built-in mechanism to do this is " merge modules" (you can build merge modules with WiX). Effectively this means that the component is registered as a shared component. ![]() The solution is generally to use the same component GUID to install the registry keys / file in both setups. The problem is that both your MSI setups think they "own" the file and registry keys in question so they happily remove them on uninstall - this is obviously clear. ![]()
0 Comments
Leave a Reply. |