>> I already HAD that line which is why most things already worked. What
>> i added was LOADHIGH E:\OS2\MDOS\MOUSE.COM to the DOS session's
>> AUTOEXEC.BAT file. It takes up almost no memory (its probably just a
>> link or for show so the prog sees a mouse) and THEN Executor works
>> fine. Loads very fast off my HPFS drive...
>
> I don't believe this is completely true... I have asked three people
>who run WARP and have tried Executor 1.99l and they don't need
>MOUSE.COM [ neither do I ] but DO need Vmouse... could it be that you
>are running a disk image, and not true mdos? I know that disk images
>that do not have mouse.com will not control the mouse properly.
>I guess this clarifies the situation [ if I am correct ]
>
>if you boot a disk image, you must have \OS2\MDOS\VMOUSE.SYS *and*
>\OS2\MDOS\MOUSE.COM, the first in your OS/2 config.sys and the second
>in your dos image autoexec.bat.
>
> --Charles
>
>P.S. Does that seem wrong to anyone?
Nope,
But i am not running a boot image, just plain MDOS. Nothin' fancy. I
do have vmouse.sys in the autoexec.bat (its there by default), but to
run Executor i NEED the MOUSE.COM from the OS2/MDOS directory in the
autoexec.bat for the DOS session. If i don't the mouse just sits in
the corner and doesn't move. This is the only program that needs the
extra mouse driver.
I'm not saying everyone needs this, but i did.
Also, MOUSE_EXCLUSIVE_ACCESS doesn't affect it since i don't run it in
a window and thus doesn't have TWO mouse cursors.
Later.
Baskin
UT Austin
Team OS/2
From owner-executor Sun Apr 9 10:09:27 1995
Received: (from majordom@localhost) by nacm.com (8.6.10/8.6.9) id KAA06530 for executor-outgoing; Sun, 9 Apr 1995 10:09:27 -0700
Received: from user33.lightside.com (user33.lightside.com [198.81.209.33]) by nacm.com (8.6.10/8.6.9) with ESMTP id KAA06520 for <executor@nacm.com>; Sun, 9 Apr 1995 10:09:14 -0700
Received: (from jehamby@localhost) by user33.lightside.com (8.6.11/8.6.9) id KAA00113; Sun, 9 Apr 1995 10:09:14 -0700