public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: setup-x86_64.exe Unable to get setup.ini on all mirrors
Date: Mon, 24 Aug 2015 17:01:00 -0000	[thread overview]
Message-ID: <87r3mshb8f.fsf@Rainer.invalid> (raw)
In-Reply-To: <55DB02CC.9080808@bellsouth.net> (Dennis Putnam's message of	"Mon, 24 Aug 2015 07:41:00 -0400")

Dennis Putnam writes:
>> 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.

Basically you can start setup.exe with direct connection (the default),
IE proxy settings or by telling it the proxy host and port.  If you have
no connection either way, then it's hard to see why only setup.exe
wouldn't connect unless you have more malware on the computer, or it's
blocked by the firewall or some similar software.

>> 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.

You didn't reboot after removing the malware via autoruns?  Then it
might still be active for already running processes.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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

  parent reply	other threads:[~2015-08-24 17:01 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
2015-08-24 14:07           ` Helmut Karlowski
2015-08-24 17:01           ` Achim Gratz [this message]
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=87r3mshb8f.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).