S
Scott
Hi all,
I'm pretty sure there is some obscure setting somewhere that controls this,
and will appreciate help finding it.
I run many custom written MS-DOS programs under XP's command prompt on many
different computers (all running XP SP2). These programs have built-in mouse
support. When the DOS program runs full-screen, the mouse *always* works on
*all* computers. However, when the application runs in a window, the mouse
*doesn't* work on a very few computers. There are one or two out of 20 or so
computers where the mouse is ignored unless the application runs full-screen.
On these machines, clicking the mouse in the application window, places a
highlighted character block on the click location, but the running DOS
program doesn't get a click code.
The DOS program is using the standard MS mouse interface (int 51) calls.
Any insight is most appreciated.
Thanks,
Scott
I'm pretty sure there is some obscure setting somewhere that controls this,
and will appreciate help finding it.
I run many custom written MS-DOS programs under XP's command prompt on many
different computers (all running XP SP2). These programs have built-in mouse
support. When the DOS program runs full-screen, the mouse *always* works on
*all* computers. However, when the application runs in a window, the mouse
*doesn't* work on a very few computers. There are one or two out of 20 or so
computers where the mouse is ignored unless the application runs full-screen.
On these machines, clicking the mouse in the application window, places a
highlighted character block on the click location, but the running DOS
program doesn't get a click code.
The DOS program is using the standard MS mouse interface (int 51) calls.
Any insight is most appreciated.
Thanks,
Scott