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: Mon, 24 Aug 2015 11:41:00 -0000 [thread overview]
Message-ID: <55DB02CC.9080808@bellsouth.net> (raw)
In-Reply-To: <op.x3ug2yjjofd6j1@nebbiolo.upc.de>
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
On 8/23/2015 7:34 PM, Helmut Karlowski wrote:
> Am 23.08.2015, 19:42 Uhr, schrieb Dennis Putnam:
>
>> Hi Helmut,
>>
>> Thanks for the reply. I can download that file but now that I have it,
>> how do I get setup to use it? However, I don't think that would work
>
> Just to test if you can access it at all but that was expectable.
OK. I have no networking problems with anything other than cygwin which
is why I was asking for someone to explain how it interfaces with the OS
network. This all started with the Lavasoft malware and I believe that
is the key to resolving this. Perhaps I'll go to one of the virus help
sites and see what they can find.
>
>> either since the problem seems to be that cygwin cannot communicate with
>> the network.
>
> You could copy the setup exe to a different name and run that in case
> setup is blocked somehow.
> First donwload it again.
No joy.
>
> Disable the firewall.
No joy
>
> You could open the taskmanager as admin and kill one obscure process
> after another and try setup again.
When I get a chance to reboot, I'll try it in safe mode with networking.
>
> Finally re-install windows ;-)
Not an option. :-(
>
> -Helmut
>
>
> --
> 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
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2015-08-24 11:41 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
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 [this message]
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=55DB02CC.9080808@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).