On Tue, 25 Jul 2006, Michael Devore wrote:

> 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.

Well, in testing GrODIN on vmware, I noticed it crashed with an illop 
right after ctmouse loaded.

-uso.

-------------------------------------------------------------------------
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

Reply via email to