Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: running the latest cygwin on a windows 2003 server Date: Tue, 20 Jan 2004 16:49:38 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <400D5539.7010809@zib.de> Message-ID: X-OriginalArrivalTime: 20 Jan 2004 16:49:38.0609 (UTC) FILETIME=[64756A10:01C3DF75] > -----Original Message----- > From: cygwin-owner AT cygwin DOT com On Behalf Of Stefan Zachow > Unfortunetly users that are not in the administrator group > cannot even start a bash. That's why I took an Administrative > user to create the cygcheck output. > The bash appears very shortly as a frame and disappears > immediately again. Tip-of-the-day: because a lot of cygwin problems manifest themselves as the shell failing to start up, and the window vanishes too quickly to see what's going on, my advice is: - start a command shell using Windoze CMD.EXE - cd - look at the commands in the cygwin.bat file, and enter them at the keyboard. This way, if there's any error message, you'll have time to read it. You can also use strace on the bash command to look for further clues hth, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/