From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Windows upgrade
Date: Wed, 13 Jun 2018 18:37:00 -0000 [thread overview]
Message-ID: <87r2lapqmu.fsf@Rainer.invalid> (raw)
In-Reply-To: <CP2P152MB1793C5EA6179682AFEA781F8DC7F0@CP2P152MB1793.LAMP152.PROD.OUTLOOK.COM> (Alejandro Benitez's message of "Tue, 12 Jun 2018 23:30:11 +0000")
Alejandro Benitez writes:
> 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).
> I'll be following the steps outlined in this post or a similar one:
>
> https://www.howtogeek.com/228042/how-to-switch-from-32-bit-windows-10-to-64-bit-windows-10/
>
> It's somehow clear I thankfully won't need to upgrade to cygwin64
> until later, I mean it seems I'll be able to still use my 32 bit
> cygwin after I upgrade to 64 bit Windows 10, I just don't know what
> I'll need to tweak / migrate so that the new Windows installation
> installed on top of the same drive that currently holds the 32 bit
> cygwin knows it's there. I'm betting some registry entries and
> environment variables. Does anyone know these tweaks for certain? I
> need cygwin to be fully functional, I mean setup.exe needs to be able
> to install packages, otherwise it won't be of much use.
You can keep using a 32bit Cygwin on any Windows 64bit desktop version
in existence so far, they all come with the WoW64 subsystem that is
necessary to run 32bit Windows applications.
> I might also be wrong and need to install cygwin64 as I upgrade
> Windows. Fingers are crossed.
However, I'd still recommend you make the switch to a 64bit Cygwin if
you have the option.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
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
next prev parent reply other threads:[~2018-06-13 17:01 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 [this message]
2018-06-15 11:17 ` Andrey Repin
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=87r2lapqmu.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).