Mark Geisert wrote:
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 syste
> 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
I just tried the latest 1.7.9-1 setup.exe (although it appears to
be the same
version used for 1.7.8-1) and get the same results for a clean
(new empty
folder) download-only operation.
Is it safe to ignore these errors in the setup log?
These look to me like they could be
On 4/1/2011 12:52 PM, Ken wrote:
Hello again,
I just tried the latest 1.7.9-1 setup.exe (although it appears to be the same
version used for 1.7.8-1) and get the same results for a clean (new empty
folder) download-only operation.
Is it safe to ignore these errors in the setup log?
These l
Ken wrote:
Hello,
Running setup.exe version 2.738 for Cygwin 1.7.8-1 on Win7-64-bit logs
numerous
"INVALID PACKAGE" entries within the "setup.log.full" file. This
seems to happen
for multiple mirrors and has been consistent for over a week now. I
do not recall
seeing this with 1.7.7-1 or ot
Hello,
Running setup.exe version 2.738 for Cygwin 1.7.8-1 on Win7-64-bit logs
numerous
"INVALID PACKAGE" entries within the "setup.log.full" file. This seems
to happen
for multiple mirrors and has been consistent for over a week now. I do
not recall
seeing this with 1.7.7-1 or other recent s
6 matches
Mail list logo
