public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: Re: NT4?
Date: Mon, 04 Jul 2011 10:34:00 -0000	[thread overview]
Message-ID: <4E106633.60804@dronecode.org.uk> (raw)
In-Reply-To: <AANLkTi=fKt8DnrkLkU5CiaBy83z_eOiwQWa8VWwvgRy5@mail.gmail.com>

On 01/04/2011 07:07, Andy Koppe wrote:
> On 31 March 2011 21:34, Corinna Vinschen wrote:
>> Is anybody here still using Cygwin on Windows NT4 on a daily basis?  I'm
>> asking because we're planning to drop NT4 support entirely and I would
>> like to know if there are lots of people who would be very sad if that
>> happens.
> 
> FWIW, NT4 support in mintty has been broken since version 0.6.1 a year
> ago, and nobody reported it until Corinna stumbled across it in NT4
> testing a few days ago.

fwiw, I thought that I might have broken XWin on NT4 recently.

On checking, I discovered that XWin has been broken on NT4 without anyone
complaining since at least 1.6.3-1, released 2009-09-06. The
VerSetConditionMask() API we use to check we aren't running on Windows 2000
isn't available on NT4. :-). Also it looks like multiwindow mode has probably
not worked correctly for longer.

> Microsoft stopped supporting NT4 in 2004.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


       reply	other threads:[~2011-07-03 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110331203416.GB2606@calimero.vinschen.de>
     [not found] ` <AANLkTi=fKt8DnrkLkU5CiaBy83z_eOiwQWa8VWwvgRy5@mail.gmail.com>
2011-07-04 10:34   ` Jon TURNEY [this message]
2011-07-04 15:19     ` NT4? Corinna Vinschen
2011-07-12  8:11     ` NT4? Ariel Millennium Thornton

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=4E106633.60804@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@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).