Hi! 28-Сен-2004 13:33 [EMAIL PROTECTED] (Michael Devore) wrote to [EMAIL PROTECTED]:
>> This is bad. :( Please, add as much, as possible, more checks before >>executing emulated instruction inside RING0, else we may/will receive >>reports about "bad FreeDOS/EMM386 behavior", whereas programs itself should >>be blamed. MD> It is not EMM386's or any memory manager's job to protect the user from his MD> or her application. In one of possible theories. But I think, environment, which, at least, _diagnoses_ incorrect situations, much more comfortable for users, than environment, which silently hangs or works incorrectly (in case of any mistake in system or application). (This is another reason, why I hate C/C++, BTW. At least, _as languages_.) MD> If EMM386 emulates all moves to and from control MD> registers and debug registers, plus covers the WBINVD and RDMSR style odd MD> values, it will be well ahead of where it is now. A number of restricted MD> opcode are meaningless in V86 mode. What good does LAR or flushing the MD> TLB's do you in V86 mode? If an application encounters that sort of thing, MD> its extremely likely to be executing garbage at that point anyway. And it MD> would be a benefit to report it as illegal opcode and terminate rather than MD> get into a complete lockup or reboot situation. This is right. But I don't say about instructions, which are invalid in V86, I say about instructions, which you wish to emulate through execution. ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel