Quote Originally Posted by Blxz View Post
I would say number 5 was the only one I had never thought of. Too large for the installer. Interesting.
Installer compilers like InnoSetup and NSIS have a limit of 2GB payload or thereabouts (before compression) because they read all the data into a memory block (memory mapped) then perform the compression and write out the result as a data section of a PE32 executable (the installer you run).

EB 2 is currently significantly larger than 2GB and certainly will grow bigger still.

Although I also didn't think much about having both steam and standard versions instealled at the same time. Is there that much difference? Couldn't you just do a system check for steam, if its installed ask the player if they want to install to their steam version. If 'Yes' then install via the steam path if 'No' then install normally. I am sure I have seen a mod do that already for me.
You could, but what about issue 10? More importantly: as you can see there are a number of “issues” which point to “location” as being one of the tough nuts to crack for installers. Suppose a user has installed Kingdoms in “C:\Program Files\SEGA\Medieval II - Total War\” and also in “C:\Program Files\Valve\SteamApps\medieval ii - total war\”, what does this scenario imply for your installer logic? This one tickles all location (related) issues you can think of...