Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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" <dk AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: running the latest cygwin on a windows 2003 server
Date:	Tue, 20 Jan 2004 16:49:38 -0000
MIME-Version:	1.0
In-Reply-To:	<400D5539.7010809@zib.de>
Message-ID:	<NUTMEGsFoai8XKPl5GD00000162@NUTMEG.CAM.ARTIMI.COM>
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 <root directory of your cygwin install>
 - 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/

- Raw text -