It makes no sense now to examine countless systems for possible misbehavior. Smarter would be to make the installer so that it runs everywhere.
In order to make an " installer that runs everywhere", one has to examine countless systems for possible misbehavior.
I'm also wondering why all the other updates have always been hassle-free and now not at all. Have you changed anything and if so, what?
We rewrote the Live Update from scratch, before users complained it was too slow.
Since the update obviously has allocation problems with installations that are NOT installed on C: - I'm NOT talking about your computer now - it would be smart to ask for user input instead to use the "full automatic" mode .
The installer obviously WORKS on every drive. And I'm not talking about "my" computer, I also talking about the computers of all our testers, and I doubt they ALL installed into C:
For example, the query for which version of the flight simulator should be updated. Here, of course, the registry can be read out and a suggestion made, but the user can change the path according to his own needs.
The place which or were the simulator is installed doesn't have any effect on the path the user is supposed to choose for FSDT.
The same can be done by querying the valid GSX installation path.
Sorry, no. The GSX path MUST the same of the last FSDT installation, and we cannot risk stuff not working, just because GSX was installed in a different folder than, let's say, JFK. They are DESIGNED to work TOGETHER.
So, the current solution is the right one:
- Leave total freedom of choice to users on the FIRST FSDT install
- Store a key in the registry about that choice.
- Automatically install into the same key all the other products.
]he problem with different registry entries to perhaps nonexistent simulator installations is then non existent.
We already fixed this.
I also think it would be wise to put just the new full installation files for downloading on the server instead of this huge live update.
That's exactly as it is now.
This certainly requires less server time than the live update with such a large amount of files.
That's why we suggested to use the Full installer, rather than the updater for THIS update. But that doesn't mean the updater won't work, it's just slower.
If the setup file does the same user queries before installation, nothing can go wrong. This gives users the freedom to decide what they want to install where. Many software manufacturers do this, e.g. REX, and there is no problem with that.
That's exactly how it is now. You have complete choice over where to install into. But all FSDT products MUST be together.