X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Mark Geisert <mark AT maxrnd DOT com>
Subject:	Re: cygwin 1.7.8-1 setup produces INVALID PACKAGE entries in setup.log.full
Date:	Tue, 12 Apr 2011 03:33:20 +0000 (UTC)
Lines:	12
Message-ID:	<loom.20110412T052647-699@post.gmane.org>
References:	<4DA0C106 DOT 7000708 AT comcast DOT net> <4DA0C121 DOT 3020306 AT comcast DOT net> <4DA0CAAB DOT 3030201 AT comcast DOT net>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

> Just for the record, on my Win7 host I am running ESET's NOD32 64-bit
> antivirus and, as a test, I had disabled that too, also to no avail.

As the FAQ entry for BLODA points out, disabling it may not be enough.  The acid
test is whether removing the BLODA from your system makes a difference.

I'm only running XP but got ESET NOD32 to behave with Cygwin by setting NOD32's
AMON (file monitor) module to exclude C:\cygwin and subdirectories.  That's
another alternative to removing NOD32.
HTH but YMMV,

..mark


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -