X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f NNTP-Posting-Date: Fri, 27 Apr 2007 00:07:13 -0500 From: "Alexei A. Frounze" Newsgroups: comp.os.msdos.djgpp References: Subject: Re: no DPMI memory under Windows vista Date: Thu, 26 Apr 2007 22:03:27 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_1839_01C7884E.B7C4E7B0" X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Message-ID: Lines: 104 NNTP-Posting-Host: 67.170.72.236 X-Trace: sv3-7tBO4Q6K4YsiBvN/CRSXn24YULERyc7cS35aYgUAAcmymGatYsl4fDzWXDK9eUN1TxV6MsWubqq71sA!yEzNLssGxT9S2JktkAYG4H6Bn1/03V8mbtFii1tmQYxDAYflBWcj1cFbZygv7WEsM2b8VQeT7KB5!Rij5Mu0T7BDGgKlZSbGjhXmNZmQjqw== X-Complaints-To: abuse AT comcast DOT net X-DMCA-Complaints-To: dmca AT comcast DOT net 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.34 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com This is a multi-part message in MIME format. ------=_NextPart_000_1839_01C7884E.B7C4E7B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable If you want both, virtual machines are the solution. Or separate = physical machines connected with a network. I remember there used to be one or maybe even more projects that could = make win32 executables out of 32-bit DPMI ones. Of course, the scope was = limited to the console apps, but it was a proof of concept that such a = conversion is possible. However, I think this days it's not gonna worh = it. It's better to redesign and reimplement the existing code to be more = portable and working on windows. I reiterate, these days windows isn't = as unexplored and scary as it was some 10 years ago. Learn message = dispatching, threads and DirectX and you'll already be able to implement = most of the DOS stuff including graphics. Alex wrote in message = news:c25 DOT 14a1eb48 DOT 336066dc AT aol DOT com... but can't we just include some old platform to support the old = DOS-programs ? switch from Vista back to an XP-like-cmd.exe and then back to Vista on = exit Even if you -maybe- could easily write Vista-programs from now on, old programs from decades of DOS-programming would be lost ! Thousands of hours of programming, research, old papers and references can't be verified etc. ------=_NextPart_000_1839_01C7884E.B7C4E7B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
If you want both, virtual machines are the solution. Or separate = physical=20 machines connected with a network.
 
I remember there used to be one or maybe even more projects that = could make=20 win32 executables out of 32-bit DPMI ones. Of course, the scope was = limited to=20 the console apps, but it was a proof of concept that such a conversion = is=20 possible. However, I think this days it's not gonna worh it. It's better = to=20 redesign and reimplement the existing code to be more portable and = working on=20 windows. I reiterate, these days windows isn't as unexplored and scary = as it was=20 some 10 years ago. Learn message dispatching, threads and DirectX and = you'll=20 already be able to implement most of the DOS stuff including = graphics.
 
Alex
<Sterten AT aol DOT com> = wrote in=20 message news:c25 DOT 14a1eb48 DOT 336066dc AT ao= l.com...
 
 
but can't we just include some old platform to support the old=20 DOS-programs ?
 
switch from Vista back to an XP-like-cmd.exe and then back to = Vista on=20 exit
 
Even if you -maybe- could easily write Vista-programs from now = on,
old programs from decades of DOS-programming would be lost = !
 
Thousands of hours of programming, research, old papers and=20 references
can't be verified etc.
------=_NextPart_000_1839_01C7884E.B7C4E7B0--