On Sat, 2002-02-02 at 16:54, [EMAIL PROTECTED] wrote: > I'm afraid I don't understand dosemu's architecture quite > enough to know what these incessant signals mean. How > would I troubleshoot this?
I was under the impression that Concurrent DOS always tries to load its own memory manager, with a DPMI "manager." This would be akin to loading EMM386.SYS under MS-DOS or DR-DOS. I've tried to figure out how to turn it off, but it seems to be ingrained into its kernel (although I'm not a Concurrent DOS expert). The memory manager, including DPMI, is already provided for by DOSEmu. Trying to load a DPMI manager (or running a VCPI program) "touches" Ring 0. Ring 0 access is not allowed, since it is controlled by the Linux kernel. Same deal with the NT kernel, and the NTDVM (NT DOS Virtual Machine) provides memory manager and DPMI for its DOS programs. -- Bryan -- Bryan J. Smith, Engineer mailto:[EMAIL PROTECTED] AbsoluteValue Systems, Inc. http://www.linux-wlan.org SmithConcepts, Inc. http://www.SmithConcepts.com --------------------------------------------------------- 1999 IRS Data: The top 1% of income earners pay over 36% of the taxes, but have less than 20% of the total income. - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
