Mail Archives: djgpp/2001/06/28/22:45:07
> If they don't act the same, then they all have quirks by which they
> can be *individually* detected.
But why? Do we really want to have special cases for *all* the DPMI
providers there are? Since they all follow the spec, why not just
code to the spec and not worry about it? Nothing in DJGPP really
cares which DPMI server you use, as long as they follow the spec.
> >dosemu (for linux, which I use)
>
> for running MS-DOS games or something, not DJGPP apps, right?
For developing/testing DJGPP itself. I use native linux for my other
projects.
> If it's something you're writing with DJGPP, you could just use
> stock gcc and get better performance under linux.
Yes, I know that. I work in the gcc development group at Red Hat.
And DJGPP's gcc *is* the "stock gcc" - the same gcc linux uses, but
for djgpp instead of linux (which is a trivial difference).
However, DJGPP's performance on a well-tuned MS-DOS machine isn't that
much worse than Linux.
> The only overlap that I can see as likely at all is Quake...
Quake I was built with DJGPP :-)
> >386MAX, QEMM, opendos, and OS/2.
>
> Does anyone *use* these obscure operating systems? Every couple of
> years I run across a reference to OS/2, that's about it.
Um, yes, because we get questions about them.
> >Plus DJGPP comes with not one but two DPMI servers
> >- cwsdpmi and pmode (if you download djgpp's unzip32.exe, you're using
> >pmode) which act differently (which is why there are two ;).
>
> And can thus be distinguished by an autodetecter.
Again - why?
- Raw text -