This is right way, I suggest. Though, I should ask: will EMM386 check instuction validness (for example, what about F0 0F C7 C8?) and how will behave system in case, when instruction will work incorrectly? As I understand, you mean instruction executing in ring 0, and here EMM386 can't trap wrong execution?
I'm only going to support common ranges for the 1-, 2- and 3- byte 0fh opcodes that are related to what's already available. Otherwise you can get goofy crashes when there's a bug or bad jump to garbage, or you never see a correctly reported bad opcode message. If it's outside the supported range it will kick out illegal feedback as before.
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
