As of 9.02, extraction of installer no longer results in the expected files (setupgs.exe, uninstgs.exe, gs9.0x). Instead it shows file0342.bin, file0343.bin, script.bin, ýŸ€, $PLUGINSDIR. This prevents manual and silent install options.
Define "extraction". The new installer does not have an "extract" option, but 7-zip can open the installer file and shows the contents as I would expect.
(In reply to comment #1) > Define "extraction". The new installer does not have an "extract" option, but > 7-zip can open the installer file and shows the contents as I would expect. (In reply to comment #0) > As of 9.02, extraction of installer no longer results in the expected files > (setupgs.exe, uninstgs.exe, gs9.0x). Instead it shows file0342.bin, > file0343.bin, script.bin, ýŸ€, $PLUGINSDIR. This prevents manual and silent > install options. Actually the new (NSIS-based) installer does allow for unattended/silent installation - I think the option is /S, the last time I looked - so manual extraction isn't necessary; the older winzipse-based installer allows for manual extraction with winzip (or winzip-compatible utilities). In both cases, the installer does not much more than extracting the files: namely a few registry entries, uninstalling, and optionally adding cjk font suport. Not too sure about setupgs.exe. setupgs.exe isn't used nor needed in the NSIS-based installer, and probably shouldn't/isn't be packaged.
(In reply to comment #2) > (In reply to comment #1) > > Define "extraction". The new installer does not have an "extract" option, but > > 7-zip can open the installer file and shows the contents as I would expect. > > (In reply to comment #0) > > As of 9.02, extraction of installer no longer results in the expected files > > (setupgs.exe, uninstgs.exe, gs9.0x). Instead it shows file0342.bin, > > file0343.bin, script.bin, ýŸ€, $PLUGINSDIR. This prevents manual and silent > > install options. > > Actually the new (NSIS-based) installer does allow for unattended/silent > installation - I think the option is /S, the last time I looked - so manual > extraction isn't necessary; the older winzipse-based installer allows for > manual extraction with winzip (or winzip-compatible utilities). In both cases, > the installer does not much more than extracting the files: namely a few > registry entries, uninstalling, and optionally adding cjk font suport. Not too > sure about setupgs.exe. setupgs.exe isn't used nor needed in the NSIS-based > installer, and probably shouldn't/isn't be packaged. Great, thank you for the information. It might be helpful to make a note of these changes in the changelog or elsewhere in the documentation. The main page still indicates that manual extraction is the correct course of action. Marked as resolved.
(In reply to comment #3) > Great, thank you for the information. It might be helpful to make a note of > these changes in the changelog or elsewhere in the documentation. The main page > still indicates that manual extraction is the correct course of action. Marked > as resolved. It is documented - quoting "Install.htm": --------------- The setupgs.exe executable in the zip file (and also in the self-extracting archive) supports a primitive form of unattended installation: if it is invoked with exactly one argument, that one argument is treated as the target installation directory for unattended silent batch installation. The NSIS-based installer (see also Release.htm supports a few standard NSIS options: /NCRC disables the CRC check, /S runs the installer or uninstaller silently, /D sets the default installation directory (It must be the last parameter used in the command line and must not contain any quotes, even if the path contains spaces. Only absolute paths are supported.) --------------- The 2nd half of the first paragraph was added after bug 691268 . I was responsible for the 2nd paragraph as well. The bug 691268 reference about documenting batch installation was in History9.htm and Details9.htm .
Thanks for chipping-in Hin-Tak, I appreciate it. Using the NSIS installer, and me taking over the Windows builds wasn't entirely planned (on my part, anyway!), and at least a release earlier than I expected, so teething problems are to be expected - there actually have been fewer than I expected. I wasn't aware that there was documentation other than the basic install, I'll try get it updated for the next release.