Hey,
Lately there has been a lot of discussion about the way DOS interrupts and
ports should be implemented. In my opinion, the best solution would be
compatible with an existing Windows API.
It seems that it would be fairly trivial to implement many of the functions
for the Windows NT Virtual Device Driver interface. In fact, most of the
functions already have an equivilant Wine counterpart.
The advantage of using the Windows NT interface is that it has already been
defined, is fairly well documented on MS's website, and is already designed
with modularity in mind. The interface would allow us to seperate all of
the DOS crap into one or many DLLs that could be loaded when required,
instead of taking up space in the core libwine.
It has been expressed several times (especially by Alexandre) that we need
to be moving towards doing things like Windows NT instead of like Windows
9x. This is one more step towards that goal. Furthermore, it would seem
necessary to have this stuff working before a version 1.0 release.
So if no-one objects, I am going to start hacking away at it.
-Dave
