From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: Cygwin-64 on W10-64 : the only game in town?
Date: Sun, 1 Nov 2020 11:23:45 +0000 [thread overview]
Message-ID: <DB7PR02MB3996CAC5666AB13289BEA8A4E7130@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20201101090012.GA3058@dimstar.local.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 1092 bytes --]
On 01/11/2020 09:00, Duncan Roe wrote:
> On Sun, Nov 01, 2020 at 08:49:23AM +0000, cygwin wrote:
>> With W7 no longer supported, W10-32 supported but no longer provided on
>> new machines (Microsoft states that, "Beginning with Windows 10, version
>> 2004, all new Windows 10 systems will be required to use 64-bit builds
>> and Microsoft will no longer release 32-bit builds for OEM distribution
>> .. the weaker version of Windows 10 has several limitations, like
>> capping out at 3.2GB of RAM and less stringent security measures") and
>> the functionality of Cygwin-32 significantly downplayed on Cygwin's own
>> Home page, that really does leave Cygwin-64 on W10-64 on 64-bit hardware
>> as the sole recommended platform. Yes?
>>
>> --
> No, I run Cygwin64 on Win 7. There is an outstanding W7 update, it appeared a
> few weeks ago, but I'm not taking it.
>
> Cheers ... Duncan.
I test my programs and compiled packages on Windows 10, 8.1 and 7. I
think Vista is still supported by Cygwin too, but last I tried it didn't
work and I can't remember why.
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-11-01 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 8:49 Fergus Daly
2020-11-01 9:00 ` Duncan Roe
2020-11-01 11:23 ` Hamish McIntyre-Bhatty [this message]
2020-11-01 15:20 ` Stephen John Smoogen
2020-11-01 16:51 ` Brian Inglis
2020-11-02 9:13 ` Corinna Vinschen
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=DB7PR02MB3996CAC5666AB13289BEA8A4E7130@DB7PR02MB3996.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).