> -----Original Message----- > From: Cygwin <cygwin-boun...@cygwin.com> On Behalf Of Bill Stewart > > On Tue, Apr 21, 2020 at 2:08 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote: > > > s/silent/verysilent/g> > > ----------- > > /SILENT, /VERYSILENT Instructs Setup to be silent or very silent. > > When Setup is silent the wizard and the background window are not > > displayed but the installation progress window is. When a setup is > > very silent this installation progress window is not displayed. > > Everything else is normal so for example error messages during > > installation are displayed and the startup prompt is (if you haven't > > disabled it with DisableStartupPrompt or the '/SP-' command line > > option explained above). > > ----------- > > > > Cygwin setup supports does not support very silent installation. > > That is our major issue describing in this thread. > > My point is that "very silent" is not necessary for automation. All you need > is > for the installer not to stop for input. > > Whether a GUI appears or not is irrelevant, as long as it doesn't block (stop > for input).
Are you sure that a setup that is automated with a silent installation, but it still displays a progress popup, it cannot fail if it is not able to display that window when there is no user logged in? I am not, hence I would prefer that setup could ensure a real background operation. An exception displaying the progress window could lead to the interruption of the installation process. That is a blocking condition as well, even though no input is required by the user. Regards, Panos Kavalagios Application Architect CONSULIAT (under contract with the EEAS) BA.BS.3.IS _____________________________________ Office: EEAS B100 Floor 5 Area 048 Rue Belliard 100, 1000 Brussels Phone: +32 2 584 6017 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
