At 09:58 PM 8/26/2005 +0200, Ladislav Lacina wrote:
Wow, it is very interresting! I don't have many experiences about ASM programming. How can I catch the opcode failing? And I can handle theese instructions myself? Even if it is not supported in the EMM386?
Umm, if you are not experienced with moderately heavy lifting in assembly language, you are not going to be able to do it. You need to be able to write several bits of low-level protected mode code to properly redirect the exception and gracefully return from it after the correct opcode emulation. Plus, patching into the EMM386 IDT might be a bit tricky, although the DOS SoundBlaster drivers do it, so it's not unexplored territory.
And anyway - I would like to know how to discrimine your EMM386 and its version. Is there any function?
Programmatic version differentiation? Can't think of one. The VDS API has a ID function which FD EMM386 could theoretically use to uniquely identify itself -- assuming I made it do so, since right now it mirrors MS EMM386 -- but if a user turns off VDS that won't help anyway. And it would only discriminate the vendor, not the version.
------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
