Brian wrote: >Upon looking at the patch again it looks like it also spits the usage >text into the setup log, which I suppose is sufficient. Much better >than having nothing.
Just to clarify, the patch actually stops the usage text going into the log. It just notes in the usage log that it is outputing the usage (next entry will be "setup is exiting"). Anyway, having diverted everyone from the "setup is broken!" threads for long enough, I think I should at least round off the thread :) I found an MSDN article on the issue from earlier this year - http://msdn.microsoft.com/msdnmag/issues/04/02/CQA/ (second question) Which echoes a suggestion from Gary V. Sickle to have two executables(http://sources.redhat.com/ml/cygwin/2004-10/msg00816.html). Igor followed up that message with some other ideas: * AllocConsole will fail if you already have one. The idea being that if you don't have a console, AllocConsole will give you one. Otherwise it won't and you use the existing one. * use AttachConsole. With setup as a GUI program, AllocConsole will always succeed (by definition). Hence you always get a new console. So this approach won't work. AttachConsole is XP/2000 only. The MSDN article above also mentions a couple oddities in behaviour. The double executable solution seems fine, but it's odd in this application. The steps would be either [download two files; run; download everything else] or [download archive; unzip; run; download everything else]. Leaving: * Print help to messagebox. Could also send it to stdout in case the user happens to be running from bash. [patches in this thread] * Make setup a console program which hides the console as soon as it determines it doesn't need it. Probably leading to Ye olde flashing console behaviour when started from the GUI. [Reini investigating] HTH, Dave. __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com
