Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!rphroy!caen!uwm.edu!ux1.cso.uiuc.edu!usenet
From: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Newsgroups: comp.windows.ms
Subject: Re: Mouse in a windowed DOS program
Message-ID: <1991Apr4.154255.14645@ux1.cso.uiuc.edu>
Date: 4 Apr 91 15:42:55 GMT
References: <1434@macuni.mqcc.mq.oz> <1991Mar31.185751.15696@uvm.edu> <1991Apr3.012535.17977@mrspoc.Transact.COM>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 41


In article <1434@macuni.mqcc.mq.oz> dcrowley@sunb.mqcc.mq.oz.au (David Crowley) writes:
>In article <1991Apr3.012535.17977@mrspoc.Transact.COM> steven@Transact.COM writes:
>>opergb@uvm.edu (Gary Bushey) writes:
>>
>>>I  have a DOS program which uses the text version of mouse and I wish to run
>>>in it in a window (I run multiple copies and compare data).  The only problem
>>>is that the mouse will not work in it.
>>>
>>>Is there any way to get this to work or am I dead in the water?
>>
>>Rather than running the program directly (or from a PIF), run a batch
>>script that first loads the mouse driver and then invokes the proram.
>
>	Even if he has loaded the driver before running the program - it
>    will *NOT* work. If the dos-app is windowed then you will *NOT* be able
>    to use a mouse with the app even if it supports it. This is because
>    windows does not release control of the mouse when you move the pointer
>    into the dos-app window. And anyhow if it did, how would windows know
>    how to get hold of the mouse again? (detect when the mouse got to the
>    edge of the dos-app? = not easy).
>							David...
>my $0.02 worth :)
>-- 
>-----------------=\|/= = = = = Don't blow up, it's more fun to implode ! = = =
>  David Crowley  --@--  Database Programmer, Macquarie University, Australia
>----------------- /|\             email: dcrowley@suna.mqcc.mq.oz.au
> At MacUni-Phone = 61 2 805-8792 Room = EsevenB 238. At home-Phone = 489-5384



There is a way. Buy a second mouse. Windows will usurp only one mouse.
I tried having one mouse on com1 and one on com2. IF I load the mouse
driver  for the non-Windows mouse after starting a DOS window then run a
text-based (or, probably, CGA-based, I have none) mouse program, it works fine.

I have two mouse cursors running around right now, one Windows, one 
in a text program in a window.


Doug MCDonald