From: Andrey Repin <anrdaemon@yandex.ru>
To: Achim Gratz <Stromeko@nexgo.de>, cygwin@cygwin.com
Subject: Re: Windows upgrade
Date: Fri, 15 Jun 2018 11:17:00 -0000 [thread overview]
Message-ID: <599847125.20180615044736@yandex.ru> (raw)
In-Reply-To: <87r2lapqmu.fsf@Rainer.invalid>
Greetings, Achim Gratz!
>> I have a 32 bit cygwin installation of 8 years of age in an amd64 PC
>> with 2 GB of RAM with Windows 10. So far it's been so good. I never
>> had the need to use a 64 bit Windows, but recently 64 bit has become
>> mainstream and I also started having low memory issues, so I upgraded
>> to 4 GB of RAM. The thing is 32 bit Windows has issues with the whole
>> 4 GB of RAM therefore I have quite less available, so I decided I will
>> be switching to 64 bit Windows 10 via a clean install (yuk!) when I am
>> able.
> Well, for an installation that old it would probably be quite helpful if
> you did a clean fresh install. A 32bit Windows can deal just fine with
> 4GB of memory (not so much with larger memory), you can make about 3GB
> of that available to user processes with a boot option (at the expense
> of memory reserved for the kernel space).
3.65GB in my experience is the best you can manage with 32-bit Windows.
--
With best regards,
Andrey Repin
Friday, June 15, 2018 4:46:46
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:[~2018-06-15 1:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 3:20 Alejandro Benitez
2018-06-13 6:12 ` Sam Habiel
2018-06-13 13:49 ` Andrey Repin
2018-06-13 14:39 ` Sam Habiel
2018-06-13 8:35 ` Andrey Repin
2018-06-13 18:37 ` Achim Gratz
2018-06-15 11:17 ` Andrey Repin [this message]
2018-06-14 1:29 ` Hans-Bernhard Bröker
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=599847125.20180615044736@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=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).