Hi Mike, > Ultimately we're going to need to have DOS device drivers that know how > to interact with the various VMs...
Only for two reasons: - the simulated hardware of the VM is "broken" so that normal drivers for the corresponding real hardware after which the simulation was modelled would fail. - we want more performance / less CPU waste caused by DOS by using more "magic VM-aware pokes" instead of lengthy I/O sequences, with hardware that is simulated anyway. I think the latter can wait more easily than the former. Even VMWare has open source mouse and X drivers around: www.vmware.com/resources/opensource/projects.html#c53533 vmmouse.c is "only" 1350 lines, the graphics driver has circa 250 kilobytes of sources in their 11.0.3 version, you can download the sources as zip/tgz/tbz from the GIT repository web interface linked from the vmware page :-) Eric PS: Bochs BIOS uses magic pokes for some ACPI stuff, so that is also an example of "more magic, easier hardware" ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
