Mail Archives: djgpp/2007/04/27/03:30:02
| X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f
|
| From: | Sterten AT aol DOT com
|
| Message-ID: | <bee.13f623fa.3362fd78@aol.com>
|
| Date: | Fri, 27 Apr 2007 03:17:12 EDT
|
| Subject: | Re: no DPMI memory under Windows vista
|
| To: | djgpp AT delorie DOT com
|
| MIME-Version: | 1.0
|
| X-Mailer: | 9.0 SE for Windows sub 5014
|
| X-Spam-Flag: | NO
|
| Reply-To: | djgpp AT delorie DOT com
|
-------------------------------1177658232
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
=20
now, what's easier to just write a patch which allows these programs to run=20=
=20
as before
or to adapt them all to the new OS ?
Just count the total programming time needed !
It probably results in many old programs no longer being available,
but well, maybe that's how Microsoft wants to hold down competing software.
=20
=20
In einer eMail vom 27.04.2007 07:19:08 Westeurop=E4ische Normalzeit schreibt=
=20
alexfru AT chat DOT ru:
If you want both, virtual machines are the solution. Or separate physical =20
machines connected with a network.
=20
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=
=20
to the console apps, but it was a proof of concept that such a conversion i=
s=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=20=
on=20
windows. I reiterate, these days windows isn't as unexplored and scary as i=
t=20
was some 10 years ago. Learn message dispatching, threads and DirectX and=20
you'll already be able to implement most of the DOS stuff including graphic=
s.
=20
Alex
<_Sterten AT aol DOT com_ (mailto:Sterten AT aol DOT com) > wrote in message=20
_news:c25 DOT 14a1eb48 DOT 336066dc AT aol DOT com_ (news:c25 DOT 14a1eb48 DOT 336066dc AT aol DOT com) ..=
.
=20
=20
but can't we just include some old platform to support the old DOS-programs=
?
=20
switch from Vista back to an XP-like-cmd.exe and then back to Vista on exit
=20
Even if you -maybe- could easily write Vista-programs from now on,
old programs from decades of DOS-programming would be lost !
=20
Thousands of hours of programming, research, old papers and references
can't be verified etc.
=20
=20
-------------------------------1177658232
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3DISO-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>
<BODY id=3Drole_body style=3D"FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY:=20=
Arial"=20
bottomMargin=3D7 leftMargin=3D7 topMargin=3D7 rightMargin=3D7><FONT id=3Drol=
e_document=20
face=3DArial color=3D#000000 size=3D2>
<DIV>
<DIV>now, what's easier to just write a patch which allows these programs to=
run=20
as before</DIV>
<DIV>or to adapt them all to the new OS ?</DIV>
<DIV>Just count the total programming time needed !</DIV>
<DIV>It probably results in many old programs no longer being available,</DI=
V>
<DIV>but well, maybe that's how Microsoft wants to hold down competing=20
software.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>In einer eMail vom 27.04.2007 07:19:08 Westeurop=E4ische Normalzeit sch=
reibt=20
alexfru AT chat DOT ru:</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><=
FONT=20
style=3D"BACKGROUND-COLOR: transparent" face=3DArial color=3D#000000 size=
=3D2>
<DIV>If you want both, virtual machines are the solution. Or separate phys=
ical=20
machines connected with a network.</DIV>
<DIV> </DIV>
<DIV>I remember there used to be one or maybe even more projects that coul=
d=20
make win32 executables out of 32-bit DPMI ones. Of course, the scope was=20
limited to the console apps, but it was a proof of concept that such a=20
conversion is possible. However, I think this days it's not gonna worh it.=
=20
It's better to redesign and reimplement the existing code to be more porta=
ble=20
and working on windows. I reiterate, these days windows isn't as unexplore=
d=20
and scary as it was some 10 years ago. Learn message dispatching, threads=20=
and=20
DirectX and you'll already be able to implement most of the DOS stuff=20
including graphics.</DIV>
<DIV> </DIV>
<DIV>Alex</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-L=
EFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV><<A title=3Dmailto:Sterten AT aol DOT com=20
href=3D"mailto:Sterten AT aol DOT com">Sterten AT aol DOT com</A>> wrote in message=
<A=20
title=3Dnews:c25 DOT 14a1eb48 DOT 336066dc AT aol DOT com=20
href=3D"news:c25 DOT 14a1eb48 DOT 336066dc AT aol DOT com">news:c25 DOT 14a1eb48 DOT 336066dc AT a=
ol.com</A>...</DIV><FONT=20
face=3DArial color=3D#000000 size=3D2>
<DIV> </DIV>
<DIV> </DIV>
<DIV>but can't we just include some old platform to support the old=20
DOS-programs ?</DIV>
<DIV> </DIV>
<DIV>switch from Vista back to an XP-like-cmd.exe and then back to Vista=
on=20
exit</DIV>
<DIV> </DIV>
<DIV>Even if you -maybe- could easily write Vista-programs from now=20
on,</DIV>
<DIV>old programs from decades of DOS-programming would be lost !</DIV>
<DIV> </DIV>
<DIV>Thousands of hours of programming, research, old papers and=20
references</DIV>
<DIV>can't be verified etc.</DIV></FONT></BLOCKQUOTE></FONT></BLOCKQUOTE=
></DIV>
<DIV></DIV>
<DIV> </DIV></FONT> </BODY></HTML>
-------------------------------1177658232--
- Raw text -