X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=I9jh7BXkpzrbb3W62Q2xSuf8gvmFcBsIPXjlnEXXlgk=;
        b=Vg5GAO08mW++sTrP77f8Wto2x2D4XfM2IUqtUYo08ekVng3aaaV/pL+MmBijYb0fGI
         ULgYwz54GKTUovOGiqAigs0GgzYz4/a39Kiw3yMHeTOP2lojXTr4SFaiUemRMsXjwZF/
         XtLXxFws2sThZIHinVmt9HMnyphJoxRddsJJpFIlFVpMsbaezzt+H9/YAWeFW1QJuq8l
         VS/wR8S+JXhjgU7xRJGsDqszgSz9WcZNHNgra+6Gsz00D2ZsVBOok0bPAZa450SpJZnC
         HNds/kkJXsSQqoWEGW70g7ZCvlHVi9If+41Lv8kIwpn+qMLR29Y3KVnZgaJzyx0TR8F1
         tDsQ==
MIME-Version: 1.0
X-Received: by 10.50.73.201 with SMTP id n9mr20658918igv.47.1445285818102;
 Mon, 19 Oct 2015 13:16:58 -0700 (PDT)
In-Reply-To: <n03cld$ebi$1@usenet.news.interia.pl>
References: <5611566C DOT 4020507 AT iki DOT fi>
	<561A4BCE DOT 7050606 AT iki DOT fi>
	<56213FE2 DOT 7090409 AT iki DOT fi>
	<562168C6 DOT 5050001 AT gmx DOT de>
	<n03cld$ebi$1 AT usenet DOT news DOT interia DOT pl>
Date: Mon, 19 Oct 2015 13:16:58 -0700
Message-ID: <CAB9Rao_ccb2QA9iLmFS2DyPsePv+oh_Ec1ZwTy9eXitwVA89SA@mail.gmail.com>
Subject: Re: Random compile errors under WIndows (32 bit Windows Vista and
 Windows 10)
From: "Louis Santillan (lpsantil AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
To: "djgpp AT delorie DOT com" <djgpp AT delorie DOT com>
Content-Type: text/plain; charset=UTF-8
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

I agree with Wiktor.  FD (or some other DOS) ought to be goal somewhere.

If, however, an XP-based OS remains a hard requirement, a guide for
Windows POSReady 2009 [0][1][2] could be developed.  It seems to be
the last XP-based OS available until 2019.


[0] https://en.wikipedia.org/wiki/Windows_Embedded_Industry#Releases
[1] http://www.microsoft.com/windowsembedded/en-us/downloads.aspx
[2] https://support.microsoft.com/en-us/lifecycle?p1=14086


On Mon, Oct 19, 2015 at 11:26 AM, Wiktor S. (wswiktorSP AT Mpoczta DOT fm)
[via djgpp AT delorie DOT com] <djgpp AT delorie DOT com> wrote:
>> AFAIK Microsoft has clearly state that they are no longer interested in
>> suporting MS-DOS applications on their OSs.
>> And all DJGPP programs are MS-DOS applications that require a full
>> functional
>> DOS environment to work flawlessly, so IMO it becomes very unlikely that
>> the
>> goal of getting DJGPP working on modern Windows operating systems can ever
>> be
>> achived.  I am not opposing on trying to get DJGPP working on Windows 10
>> or
>> similar OS but in consideration of the fact of the small amount of DJGPP
>> users
>> and the even smaller amount of skilled DJGPP developers really familiar
>> with
>> DJGPP internals and Windows internals, this will take at least a couple of
>> months
>> more, probably it will take years.  IMO, an attempt to get DJGPP working
>> on
>> Windows 10 or similar operating systems shall be postponed until 205 has
>> been
>> released.  The over the years vanishing group of DJGPP users do not
>> deserve to
>> wait until the end of days for this release.  I really think that we shall
>> take
>> seriously user questions like this one:
>
>
>
> It's obvious that MS has no intention to bring NTVDM back to its glory.
> But sticking to Windows XP as the "last good OS" is as slow path to death of
> DJGPP.
> If there is to be any future of DJGPP (a very limited one, but still a
> future), the project has to embrace what is still alive: DOSBox and FreeDOS.
> Full compatibility may require a cooperation with those projects'
> developers, and fixing some things on their sides too, but at least those
> *can* be fixed, unlike Windows.
>
> A mid-term goal should be a successful build of DJGPP/gcc/binutils on
> FreeDOS (as I understand it doesn't work right now).
>
>
>
> --
> Wiktor S.
>