Hi man, 23,.01.2006 kl. 23.20 +0100, skrev Salvo Isaja:
> Please remember that the goal of this PIT driver is to be > DOS-compatible. In fact, it still isn't, because several things are > expected to be done, like turning off the motor for INT 13h, setting > the BIOS time-of-day and calling INT 1Ch. Otherwise we may call the > original real-mode INT 8 handler. > As Hanzac has pointed out, multitasking DOS/DPMI apps without any form of virtualization is a problem, but IMHO that need not get in the way of sequential execution of DPMI and native apps. Instead of one module for DOS compatibility and other modules for higher resolution/accuracy, couldn't there be a single module with different operating modes, and have a "syscall" for switching between the modes, to be called by the native app or the DPMI driver? The way the situation is now, if I have written a native app with stricter timing requirements but want to execute DOS/DPMI apps before and after the native app, then I have to let the native app reprogram the timer itself (or reboot to load a different timer module). Nils ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ freedos-32-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-32-dev
