X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f NNTP-Posting-Date: Wed, 09 Feb 2011 22:33:38 -0600 From: "Charles Sandmann" Newsgroups: comp.os.msdos.djgpp References: <125997 DOT 8962 DOT qm AT web45113 DOT mail DOT sp1 DOT yahoo DOT com> Subject: Re: VIRTUAL BOX and my GAME - Mr Rod Pemberton Date: Wed, 9 Feb 2011 22:32:34 -0600 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 X-RFC2646: Format=Flowed; Original Message-ID: Lines: 30 X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 64.91.136.221 X-Trace: sv3-FilUenrzC44q8yBGtRECPPa2vwHynsMaxYOg7GYEmbWYLtyIKLdoD70yyOqJLzv9RdumwLD3QW+asWv!8ltb/SjPrG6flyclXt4fU4fGa+I/94EE5DgKgKFy+T9Rq+cV/nbLTcheiPhenBPZhj7AnI0mt5yC!YmarfFtfjsSZExOAcAXoXJl608m9G1FX X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 Bytes: 2595 X-Original-Bytes: 2534 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > (djgpp) tried to move to XP, sort of... It hasn't, yet... I've been using v2.03 without issue for 9 years now on XP, so this is just wrong. > That's still in Beta. 7 years of Beta... No demand? v2.04 has been in beta for around 9 years. No one has wanted it bad enough to complete it. DJGPP is a volunteer effort. Some people have claimed the justification for v2.04 was better XP support, but I have never agreed with that opinion. v2.04 does have much more support for recent function calls, which makes porting recent "linux only" type software easier. > I've repeatedly suggested two things that could > breathe some life into DJGPP: GNU GLIBC, and recompiled v2.03 with 64-bit > support enabled. GLIBC would allow GNU tools on DOS to just work. 64-bit > would allow current users to migrate from 32-bit. DJGPP is build on a DOS API, which requires a 16-bit DOS. 64-bit OSes cannot run 16-bit apps directly (this is a hardware limitation) - so it would all need to be emulated (SLOW), and would not launch seamlessly like 16-bit apps currently do under 32-bit Windows. Moving to a different API is a complete re-write. If you need to run on 64-bit windows, you need applications built with a a different run-time to use the Windows native API (either the 32-bit or 64-bit).