X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Installation problem on windows 2000 server
Date:	Thu, 30 Mar 2006 12:08:00 +0100
Message-ID:	<063b01c653ea$350599d0$a501a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
In-Reply-To:	<442B48E2.20204@qnorth.net>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On 30 March 2006 03:57, jack wrote:


> Should I post this question on another cygwin list? Or does nobody have
> experience with this kinda thing?


  Get that non-cygwin perl out of your path and try using setup.exe to
reinstall everything.  Make sure - using task manager if need be - that there
is absolutely no trace of any cygwin-based programs or services running.

  Antivirus and desktop firewall software can both interfere with the
successful operation of cygwin, particularly if it's one of the
supposedly-clever behaviour-blocking varieties, so watch out for that, and
make sure that nothing has been inadvertently blocked; if so remove it before
you try again.

  Probably the next most likely possibility is that the machine itself is
terminally b0rken.


    cheers,
      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 -