From: Helmut Karlowski <helmut.karlowski@ish.de>
To: cygwin@cygwin.com
Subject: Re: setup-x86_64.exe Unable to get setup.ini on all mirrors
Date: Mon, 24 Aug 2015 14:07:00 -0000 [thread overview]
Message-ID: <20150824160726.8A755800.helmut.karlowski@ish.de> (raw)
In-Reply-To: <55DB02CC.9080808@bellsouth.net>
Dennis Putnam
Mon, 24 Aug 2015 07:41:00 -0400
---------------------------------------------------
> OK. I have no networking problems with anything other than cygwin which
Another idea:
You could download the packages needed for a basic install from any
server, e.g.:
ftp://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/
and save them under a new directory (not \cygwin!) while keeping the
directory-structure intact. Then run setup and tell it to install from
that local directory. Surely not comfortable, but if you succeed
you'll have learned something about cygwin :)
I once did that on a PC without internet, but then I had my
cygwin-download-directory from the other PC on USB.
Maybe the windows-ftp-tool can help you to download, I don't know.
> 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.
You should do that.
> > 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.
Maybe autoruns sheds some light?
https://technet.microsoft.com/de-de/sysinternals
Or msconfig?
-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
next prev parent reply other threads:[~2015-08-24 14:07 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 [this message]
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=20150824160726.8A755800.helmut.karlowski@ish.de \
--to=helmut.karlowski@ish.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).