X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=DyxP92v
	sZXW2jpBXKJ8/prgAuHMWa7RKC1ki3OXllo2+D0Jr/g3nkgT9G4qo3uIZfAmXq4G
	MultnFb9FhmHONwtEpgcT08BmWtgWdtih3QTkGlkI021OksFqkyRtohP3umlxK3F
	DwdGhvwwnUKBHOdsylgCQDiu0VXnINb9PEzs=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; s=default; bh=NWpV5vhhfAjuJ
	b0pLlUDCGz9z0s=; b=A7tQ8zv/qeDDgboTtbnAMQJjoSsFgXAo75iL35Nqf8A3i
	CqhTlb+uqRnUmjhkiEiqlgY5OBf53obZupCB3caVG5aV2XLv1jSaEtAP5TqrBUWA
	2/Ui4NbJKFgsmMS8mo8G2858jzqCqYQv6S0Xym2E0vzXihOkRF6vuh53J7gYE8=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=HX-Received:sk:p1-v6mr, H*c:alternative, age
X-HELO:	mail-wm0-f50.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=URqI2HFsgxrAKzUOZ6tRubAU6TgqZhap/w7pExCqeEM=; b=s90CFJqFuGjQIartow5LzW1l0L6ahEf2xSQ2uREog4JE9jMS6NNIcqvVp5CQSN+puV /WIlY9UVoByA34I9QbVEsUfmJrAwgRPo8JnNKoZ8re9hBTFjRZ68xzdRcOr1TFriCeph 5ZB6BCCNDGy8BgLBmKgwI21JYc+SATYPxpmPma5S6nZIhUc3BJTjL79RrGXarptYszCu MlwYTIi4qtT5LiFTuNs9q5obu5nfpxUvOrmJCXnM34pX+2+0APBEkHjJ3idNLbCgRcuV NI4RVPxRNv0wwjKqkKXqh7hwa0jmoGGm4C4qmOI1afOZwTlVJrqrE0Qgst2HlFWN61KZ 5oqg==
X-Gm-Message-State:	APt69E2imIUN566INiRc2DQKj6zoi+DtEyPg8/pVsCFQN5IcL13HLclk dsygVuDVnOBM7ygd3+l+rFLwPlRWiZ+eX8T1jeRlPw==
X-Google-Smtp-Source:	ADUXVKJjmoJykuvI0IL1hwJcOXoWJSHeuhtJ8EEtMfaEcTmJBaMjNRvOWJs9dVUJjp2mm5hkSwZwh1EVWOEefc5afTE=
X-Received:	by 2002:a1c:7401:: with SMTP id p1-v6mr1937833wmc.14.1528850663845; Tue, 12 Jun 2018 17:44:23 -0700 (PDT)
MIME-Version:	1.0
References:	<CP2P152MB1793C5EA6179682AFEA781F8DC7F0 AT CP2P152MB1793 DOT LAMP152 DOT PROD DOT OUTLOOK DOT COM>
In-Reply-To:	<CP2P152MB1793C5EA6179682AFEA781F8DC7F0@CP2P152MB1793.LAMP152.PROD.OUTLOOK.COM>
From:	Sam Habiel <sam DOT habiel AT gmail DOT com>
Date:	Tue, 12 Jun 2018 20:44:13 -0400
Message-ID:	<CABHT960wyrxvRiC-V2m5f=Z0gi4inKvyjXZ1E1ERAWUM9-Nf_A@mail.gmail.com>
Subject:	Re: Windows upgrade
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

I use Cygwin 32-bit all the time on Windows 10 x64.

--Sam

On Tue, Jun 12, 2018 at 7:31 PM Alejandro Benitez <
BenitezAlejandroeepo AT outlook DOT com> wrote:

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

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

- Raw text -