[Prev][Next][Index][Thread]

Re: Executor and Warp?



> 
> On Sat, 8 Apr 95 14:26 MDT you wrote:
> 
> >
> >
> No, no,
> 
> 	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?

> 
> Later.
> 
> 
> Baskin
> UT Austin
> Team OS/2
> 



References: