From: Dennis Putnam <dap1@bellsouth.net>
To: cygwin@cygwin.com
Subject: Re: setup-x86_64.exe Unable to get setup.ini on all mirrors
Date: Sun, 23 Aug 2015 13:21:00 -0000 [thread overview]
Message-ID: <55D9C8F2.4090608@bellsouth.net> (raw)
In-Reply-To: <55D5E2D2.1040308@bellsouth.net>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
Since I have gotten no response to this and am stuck I assume my problem
is badly worded. I don't know how else to present it. Perhaps someone
explaining how setup uses the windows network interface would help.
If it helps, I tried installing Cygwin from scratch and it will not even
download the list of mirrors. If I add a specific mirror I get the same
subject error message. Clearly setup is having trouble communicating on
the network and it is probably related to something left over from the
Lavasoft malware but I don't know what to do from here. I've used every
cleanup tool I have and there does not appear to be anything related to
Lavasoft left.
On 8/20/2015 10:23 AM, Dennis Putnam wrote:
> In the process of correcting another problem (removed Lavasoft malware)
> I am no longer able to run setup. All the references to this error seem
> to pertain to the 32 bit version. I am completely shutdown with Cygwin
> and need help resolving this. Thanks in advance.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2015-08-23 13:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 14:23 Dennis Putnam
2015-08-23 13:21 ` Dennis Putnam [this message]
2015-08-23 14:00 ` Helmut Karlowski
2015-08-23 18:42 ` Dennis Putnam
2015-08-23 23:34 ` Helmut Karlowski
2015-08-24 11:41 ` Dennis Putnam
2015-08-24 14:07 ` Helmut Karlowski
2015-08-24 17:01 ` Achim Gratz
2015-08-24 17:16 ` Dennis Putnam
2015-08-24 17:42 ` Achim Gratz
2015-08-24 17:46 ` Dennis Putnam
2015-08-24 18:36 ` Michael Enright
2015-08-24 18:35 ` Andrey Repin
2015-08-24 18:45 ` Dennis Putnam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55D9C8F2.4090608@bellsouth.net \
--to=dap1@bellsouth.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).