From: Andrey Repin <anrdaemon@yandex.ru>
To: "KARR, DAVID" <dk068x@att.com>, cygwin@cygwin.com
Subject: Re: New cygwin install hanging on postinstall
Date: Fri, 22 Jan 2016 17:32:00 -0000 [thread overview]
Message-ID: <737198364.20160122103452@yandex.ru> (raw)
In-Reply-To: <B8D164BED956C5439875951895CB4B2250BB0354@CAFRFD1MSGUSRJH.ITServices.sbc.com>
Greetings, KARR, DAVID!
>> > I was installing cygwin for the first time on a Win7-32bit box.
> It has 4g RAM. Checking "Resource Monitor" while the install is running, there is 750MB "available".
How much memory is "available" is not an indication for a 32-bit OS. You
simply can not allocate more than 2GB of RAM to a single process without much
hackery. Which means, certain applications could hit a roadblock just because
of that. Same applies to your 4GB statement: You just can not use it all with
32-bit OS without much hackery on OS level, and that means slowing down entire
system.
You are really, really want 64-bit OS with more than 2GB RAM to see any light
at the end of the tunnel.
On top of that, if you are still struggling with installation, and hints
offered in other messages did not helped to date, the most simple way would be
to eliminate the failed Cygwin install and start anew, this time only install
a base (setup default) set of tools first time, may be accompanying them by
choice things of convenience, like wget and/or procps. But nothing overgrown
like TexLive.
--
With best regards,
Andrey Repin
Friday, January 22, 2016 10:27:27
Sorry for my terrible english...
--
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:[~2016-01-22 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 5:34 KARR, DAVID
2016-01-21 5:42 ` Stephen John Smoogen
2016-01-21 19:09 ` KARR, DAVID
2016-01-21 21:29 ` Ken Brown
2016-01-21 21:51 ` Achim Gratz
2016-01-22 3:12 ` KARR, DAVID
2016-01-22 7:30 ` David Stacey
2016-01-22 17:32 ` Andrey Repin [this message]
2016-01-22 18:50 ` KARR, DAVID
2016-01-22 20:07 ` Mark Geisert
2016-01-22 20:14 ` Andrey Repin
2016-01-21 8:02 ` Ken Brown
2016-01-21 13:18 ` Achim Gratz
2016-01-21 21:17 ` Ken Brown
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=737198364.20160122103452@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=dk068x@att.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).