This is the mail archive of the
mailing list for the Cygwin project.
Re: cygwin 1.7.8-1 setup produces INVALID PACKAGE entries in setup.log.full
- From: Ken <kstmp001 at comcast dot net>
- To: cygwin at cygwin dot com
- Date: Fri, 22 Apr 2011 16:38:30 -0400
- Subject: Re: cygwin 1.7.8-1 setup produces INVALID PACKAGE entries in setup.log.full
- References: <4DA0C106.email@example.com> <4DA0C121.firstname.lastname@example.org> <4DA0CAAB.email@example.com> <loom.20110412T052647firstname.lastname@example.org>
Mark Geisert wrote:
Thank you for your suggestions and reminder regarding the BLODA FAQ.
Although I have not yet resolved the
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,
original issue, it appears that the problem is exhibited only when
reading/writing to my internal disk array (simple
RAID1) but works flawlessly with external devices (USB flash or hard
drives). Otherwise, my system is extremely
stable and all array and disk diagnostics pass. And, since the download
used to complete error-free when storing
to my array, I suspect that it is due to some BIOS or driver update I
had applied over time; but I have not had the
time to devote backing them out to determine which one. I will endeavor
to isolate the cause at some point.
Therefore, it is my assertion that this is *not* a cygwin setup.exe
issue after all. I wrote back to the list simply to
close the loop and to thank you for your time.
Again, thank you,
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple