June 2, 200521 yr Commercial Member I'm looking for an installer suitable for payware scenery supplied on CD.The scenery is a bit of a tight fit, so good compression is a requirement.Anyone have a choice they swear by?-RobinVisit the Windowlight forum on Avsim... everything you need to know about New Zealand flightsim sceneryhttp://forums.avsim.net/dcboard.php?az=sho...forum=203&page=
June 3, 200521 yr An excellent choice is NSIS.Clean, reliable and VERY powerful. With NSIS you can do anything!It has a comprehensive list of features, including the amazing LZMA compression! (very powerful) ;) And the best: NSIS is open source and fully freeware!Actually NSIS is better than many payware installers I know (I have used many), and is super reliable.NSIS is script-based. You must write a text file in order to define the installation details.Actually this is not a problem for most users, which are professional developers (programmers). In fact, the script-based definition makes NSIS more powerful than many non script-based ones.http://nsis.sourceforge.net/featureshttp://nsis.sourceforge.net/P.S.: I used NSIS for FSDEM, my freeware add-on for FS. I use it at job as well.
June 4, 200521 yr Author Commercial Member Thanks for that, it does look like it can do everything I want. It works great on a small project, but I get an out of memory error on the main package. It gets most of the way through, but I guess it chokes on my 18000+ textures...
June 4, 200520 yr >It works great on a small project, but I get an out of>memory error on the main package. It gets most of the way>through, but I guess it chokes on my 18000+ textures...How many megabytes is your data?There's a size limit (2GB) for single EXE file installer (everything in a single EXE file). I found this excerpt from their FAQ: (see the last paragraph)"I get an error when compiling large installersNSIS can theoretically compile installers as large as 2GB. This is first limited by the amount of free disk space on the drive containing the system temporary directory. To get the best results, this drive must be formatted as NTFS and must have enough free space to hold the temporary file, which can get upto 2GB depending on the packed files. This means you can't compile very large installers on Windows 9x because it doesn't support NTFS. The limit is about 700MB on a FAT partition. More RAM and virtual memory will only help speed up the process but won't increase the limit. When distribution very large data, it's usually better not to store everthing in the executable file, but store the data separate and use CopyFiles or extraction plug-ins to install."
June 4, 200520 yr Author Commercial Member Thanks for that, I did intend to go searching for a solution, but too much on my plate at the moment.The total install is only about 735MB. I normally have 20+GB free, on NTFS, and 1GB RAM. I do think that it has more to do with the number of files, so I'll work on that.
August 16, 200520 yr I've been playing with Inno Setup recently and it appears to be wonderfully full-featured. So far have only used it for VB application setups but it seems to do much more and.....it's freeware.Art
November 4, 200520 yr I am a HUGE fan of Clickteam's Install Creator. It is cheap for the registered version, and they even offer a free version with all of the functionality and just has a small advertisement at the end of the installer. I use Install Creator for all of my add-ons and haven't had a single problem yet.It is availible at http://www.clickteam.comCheers, :-beerchug Sean
December 1, 200520 yr >I've been playing with Inno Setup recently and it appears to>be wonderfully full-featured. So far have only used it for VB>application setups but it seems to do much more and.....it's>freeware.>>ArtArt; I just got into INNO myself -- how much have you learned about it? In designing an old SAC airbase (Pease AFB NH, closed 1991), I have to either move the default BGL out of SceneryNameScenery to a directory FS9 doesn't access, or rename the default BGL to something that FS9 won't recognize; otherwise, there will be texture, NAVAID, and other conflicts between the default and the new KPSM.I'm just beginning to get into script writing, but could use some help on figuring out if, during part of the installation process by those who download the package, INNO can either "move" a designated file to another directory or "rename" that file to something else?Appreciate anything you offer on this as that default MUST be moved for my recreated airbase to function correctly.
Create an account or sign in to comment