Mail Archives: djgpp/1997/04/16/00:59:09
>I don't know if things are as clear as you suggest. Who knows, maybe
>someone could figure out a way to use a DirectX driver in a DOS program.
>I agree that it would be very difficult and highly unlikely, but it
>would
>doubtlessly be useful for people in DOS wanting to support the latest
>hardware.
It wouldn't be difficult to figure out at all, just time consuming since
you'd
have to reinvent windows. What's the point? You already got windows. It
doesn't matter what that driver was MEANT to do, the point is you don't
know what it DOES do, and they could use ANY aspect of windows they
wanted to make their driver work the way it does, and especially when
it comes to resource management, interrupts settings, interfacing with
the monitor, etc. etc. Do you want to recode all those portions of
windows?
You might as well rewrite windows before even bothering.
>A year ago I never would've thought that a DOS program could use Win95's
>communications abilities to work over the Internet. Then Quake came out
>and I watched the MPath Winsock Tunnel give it this power. In fact,
>just yesterday I found the WSOCK library for DJGPP. One of the sample
>applications is a DOS web server for Win95. Scary, eh? (The WSOCK
>library is at http://www.rangenet.com/markiv in case anyone wants it..)
Quake doesn't implement a Windows Socket Driver in dos, which is the
equivalent to the DirectX driver problem. Quake simply uses the windows
driver while Windows is running. If windows isn't running, Quake can't
use
it. Quake did nothing spectacular there.
I've suggested it before anyways. Why not just run Allegro as a Windows
95 Console program and use the DirectX features that way? That makes the
most sense to me! You get the best of both worlds w/o all the fuss of
the Windows 95 interface (unless of course someone wants to add
support in to DJGPP, which I'm hoping is a reality soon).
- Raw text -