DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=I+D
	X9kcthoY+u2pMBQ/DZsXr9fm0k6Hhyq5Wjmq0oq6h1hajLflL138o2BMPx4k2zl7
	dCPBqP4L5LWZ9SFk1iLEi5K2VYhizj0yPoC4WEYJ/5UM4uJ12oJaGjOAt1Pjtul6
	kLlt6v4nnOATa3NkorzDGnTIbXaSdoURUN26xkN8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Alejandro Benitez <BenitezAlejandroeepo AT outlook DOT com>
To: cygwin <cygwin AT cygwin DOT com>
Subject: Windows upgrade
Date: Tue, 12 Jun 2018 23:30:11 +0000
Message-ID: <CP2P152MB1793C5EA6179682AFEA781F8DC7F0@CP2P152MB1793.LAMP152.PROD.OUTLOOK.COM>
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [LaFyIE1rHPqXzzUBzJzF3KiiRSx/bfri]
x-ms-publictraffictype: Email
x-incomingheadercount: 47
x-eopattributedmessage: 0
x-ms-traffictypediagnostic: CO1NAM04HT202:
x-forefront-prvs: 07013D7479
received-spf: None (protection.outlook.com: outlook.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=BenitezAlejandroeepo AT outlook DOT com;
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: d7832d16-22b3-49d9-588f-08d5d0bc6fdc
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 5dab7a8a-ebdc-4bd9-9cfd-67cde50b170b
X-MS-Exchange-CrossTenant-Network-Message-Id: d7832d16-22b3-49d9-588f-08d5d0bc6fdc
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 5dab7a8a-ebdc-4bd9-9cfd-67cde50b170b
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jun 2018 23:30:11.4590 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1NAM04HT202
Content-Type: text/plain; charset="Windows-1252"
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id w5CNVC5X008254

Hi,

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.

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.

I might also be wrong and need to install cygwin64 as I upgrade Windows. Fingers are crossed.

Thanks in advance,

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