Isn't it more logical to change ctmouse then? Imre
>-----Original Message----- >From: Michael Devore [mailto:[EMAIL PROTECTED] >Sent: Wednesday, July 26, 2006 05:35 AM >To: freedos-devel@lists.sourceforge.net >Subject: [Freedos-devel] 2nd FreeDOS 1.0 Testing release > >At 09:48 PM 7/25/2006 +0200, Japeth wrote: >> > >> > QEMU has never liked CTMOUSE under FreeDOS, and possibly MS-DOS. I don't >> > know why. >> >>when I modify emm386.asm, proc v86_monitor, so that the IF in real-mode is >>cleared for all interrupts routed to v86-mode, not just the IRQs, it works >>with CTMOUSE in qemu. >> >>There might be good reasons to clear IF for IRQs only, as it is done in >>current source code. > >Here's my initial problem with this idea: it works when you get step >outside of the Qemu DOS sandbox. Plus it works (or worked) in Bochs, since >I remember testing it under Linux a year or two ago when trying to figure >out what the heck was going on with CTMOUSE and Qemu. And it only seems to >fail with CTMOUSE and not other programs which use interrupts a lot more >creatively. (I should check VPC 2004 now and see which side of the fence >it falls on). > >So, is there a real bug normally masked in some way, or an optional >behavior, or a situation which only fails in (or due to) a particular >virtual environment? And if does only fail in a virtual environment, what >effect would changing the behavior have in real/nonvirtual DOS and a >bazillion working applications? > >Changing a long-standing fundamental behavior to fix a single problem in a >virtual environment with one program can be worrying. I'd feel more >confident about making an immediate change if someone could point to a >program or test which fails under a nonvirtual environment due to the IF >status, or if they demonstrated widescale failure in a virtual >environment. Even better would be a good explanation for why the problem >only manifests itself with that specific environment and application. > >Unless there's a quick answer here by someone with the experience or >expertise on the issue, it may take some study to answer the questions to >my satisfaction and decide on making your suggested change. > > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys -- and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >Freedos-devel mailing list >Freedos-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/freedos-devel > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
