X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Received:	by 10.129.73.211 with SMTP id w202mr23739654ywa.40.1441828489954;
	Wed, 09 Sep 2015 12:54:49 -0700 (PDT)
X-Received:	by 10.182.241.67 with SMTP id wg3mr150704obc.15.1441828489891;
	Wed, 09 Sep 2015 12:54:49 -0700 (PDT)
Newsgroups:	comp.os.msdos.djgpp
Date:	Wed, 9 Sep 2015 12:54:49 -0700 (PDT)
In-Reply-To:	<1074050599.3777568.1441819933600.JavaMail.yahoo@mail.yahoo.com>
Complaints-To:	groups-abuse AT google DOT com
Injection-Info:	glegroupsg2000goo.googlegroups.com; posting-host=78.42.224.25; posting-account=OsAajgoAAADdKJnkJkmhzqP0jo6I_P_0
NNTP-Posting-Host:	78.42.224.25
References:	<55E17D7D DOT 4030406 AT gmx DOT de> <1074050599 DOT 3777568 DOT 1441819933600 DOT JavaMail DOT yahoo AT mail DOT yahoo DOT com>
User-Agent:	G2/1.0
MIME-Version:	1.0
Message-ID:	<396612cd-31a1-46bc-ae2a-74c8b104783d@googlegroups.com>
Subject:	Re: ANNOUNCE: DJGPP 2.05 release candidate
From:	"Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Injection-Date:	Wed, 09 Sep 2015 19:54:49 +0000
Bytes:	6259
Lines:	140
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t89KF2XM022293
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

On Wednesday, September 9, 2015 at 7:45:47 PM UTC+2, Peter Bailie (prbailie AT yahoo DOT com) [via djgpp AT delorie DOT com] wrote:
> Juan,
> 
> 
> Is this new release compatible to 64 bit operating systems?  If it is do I go to the link you show in your email?
> 
> 
> Thank you.
> 
>   
> 
> 
> 
> 
>  
>  
>  
>   On Saturday, August 29, 2015 2:43 AM, "Juan Manuel Guerrero (juan DOT g DOT  DOT  DOT  AT gmx DOT de) [via dj DOT  DOT  DOT  AT delorie DOT com]" <dj DOT  DOT  DOT  AT delorie DOT com> wrote:
>     
> 
>  
> Am 09.06.2015 18:33, schrieb Andris Pavenis (andris DOT  DOT  DOT  DOT  AT iki DOT fi):
> 
> > This is announcement of release candidate of DJGPP 2.05
> >
> > It has numerous changes since previous DJGPP 2.04 beta 1 release in 2003.
> > (http://www.delorie.com/djgpp/mail-archives/browsecgi?p=djgpp-announce/2003/12/06/22:18:05)
> > Unfortunately DJGPP v2.04 was never released and old beta version slowly
> > became almost unusable together with other newer DJGPP packages.
> >
> > More information about changes in DJGPP 2.05 is available at
> >
> > http://www.delorie.com/djgpp/doc/kb/
> >
> > both in sections about changes in 2.04 and 2.05. The same information is also
> > available in file info/kb.inf in djdev205.zip
> >
> > It is expected to become actual release unless critcal bugs will be found.
> >
> > Note that one should use djgpp v2.05 RC with other binary packages from
> > ftp://ftp.delorie.com/pub/djgpp/beta and NOT (ftp://ftp.delorie.com/pub/djgpp/current).
> >
> > The release candidate versiona is not available via the Zip Picker interface.
> > You can download it from here:
> >
> > ftp://ftp.delorie.com/pub/djgpp/beta/v2
> >
> > Additionally RPM packages (source and binary packages for i686 and x86_64) are
> > available from
> >
> > ftp://ftp.delorie.com/pub/djgpp/rpms
> >
> > Binary RPM packages are built in such way that they are expected to install and
> > work on any recent enough RPM based Linux distribution (for example RHEL5 and newer
> > should be OK, RHEL4 perhaps not)
> >
> > Please see the README file for instructions on how to install the beta:
> >
> > ftp://ftp.delorie.com/pub/djgpp/beta/v2/readme.1st
> >
> > You can also download DJGPP 2.05 release candidate 1 from DJGPP mirror sites:
> >
> > http://www.delorie.com/djgpp/getting.html
> >
> > Thanks for all who have contributed to development of DJGPP
> >
> > Andris Pavenis
> >
> 
> 
> During this week-end I will update the complete DJGPP distribution to DJGPP 2.05.
> This includes the rebuilding of all dj*zip archives so the lates changes of the
> v2_05_1 branch is in the library and the moving of all new archives from the /beta
> tree into the /current tree.  Obsolete archives from the /current tree will be moved
> into the /deleted tree.  Obsolete archives from the /beta tree will be moved into
> the /deleted/beta tree.  Nothing will be lost.
> 
> I will keep the latest version of every compiler serie.  A compiler serie is defined
> by its last version digit.  E.g. if there are gcc200, gcc201, gcc202, gcc205 then I
> retain gcc205 and all the other ones will be moved into /deleted.  Attention: gcc20X
> is a different serie than gcc21X.  This has the consecuence that a lot of compiler
> versions will remain in the /current directory.  If this is not wanted this is the
> last occasion to speak.
> 
> To fullfill this task I will use a slightly modified version of the script proposed in:
>    http://www.delorie.com/archives/browse.cgi?p=djgpp/2015/08/16/08:08:18
> I have got neither a positive nor a negative reponse to that proposision so I will assume
> that all agree and I will go ahead.
> 
> I still have to do some preparations for all this, and that will take the rest of the day.
> During this day I will wait for objections or suggestions and tomorrow I will update the
> /current directory if there are no ____really serious____ objections.
> 
> 
> Regards,
> Juan M. Guerrero

No, DJGPP is a system to produce 32-bit binaries to be run on DOS-like operating systems.  This includes NTVDM as provided by Windows XP and previous Windows versions.  Please read http://www.delorie.com/djgpp/ for more information.  I have never used Windows Vista or later Windows versions so I cannot tell how good the DOS emulation of those NTVDMs is and thus if DJGPP binaries run on Vista.  Anyway the DJGPP produced binaries have a 16-bit stub to be started and thus every Microsoft OS without 16-bit support will not be capable to run DJGPP.  Neitherless there are a lot of people that produce cross-compilers to create DJGPP binaries.  These binaries target some kind of DOS system and certainly not the 64-bit OS used to run the cross-compiler.  They use 64-bit OS to produce binaries not to run them on that 64-bit OS.

Regards,
Juan M. Guerrero

- Raw text -