Sender:	nate AT cartsys DOT com
Message-ID:	<358EC752.8059D549@cartsys.com>
Date:	Mon, 22 Jun 1998 14:06:26 -0700
From:	Nate Eldredge <nate AT cartsys DOT com>
MIME-Version:	1.0
To:	"Kertis A. Henderson" <kertis AT frozenwave DOT com>
CC:	djgpp AT delorie DOT com
Subject:	Re: djgpp and Linux DOSEmu
References:	<358B2BCE DOT 940C4085 AT frozenwave DOT com> <358D6412 DOT F0B32FC1 AT cartsys DOT com> <358D8327 DOT 938E53D AT frozenwave DOT com>

Kertis A. Henderson wrote:
> 
> Nate Eldredge wrote:
> >
> > Kertis A. Henderson wrote:
> > >
> > > Hello.  I recently installed the latest DOSEmu for linux, and the first
> > > this that I installed was djgpp (or course).
> >
> > What do you consider the "latest"?  I believe they have both "stable"
> > and "development" versions.  The latest stable (I think) is 0.66.7,
> > while development should be around 0.99.x
> 
> I'm using the latest stable version I could find.  I think that it would
> have been a bad idea to post a question about the development version.

Okay.  I asked because there have been several postings lately from
people using development versions.

> > I use 0.66.7, and for me the mouse doesn't work correctly at all.  It
> > might be time to upgrade...
> >
> > Also, I expect that any program that tries to use the timer won't work.
> 
> Would the mouse and timer problem be related?

Actually, I was wrong about that.  I've had another look; it seems that
the mouse emulation under X is imperfect-- it just jumps around.  When I
run on the console, using BIOS video and a DOS mouse driver, the mouse
works fine in 320x200, though a little slow.  In VESA modes, it does
indeed crash the test program (though I can't tell if it's the mouse
that does it).  I haven't looked into the precise reason behind this. 
But when I use higher modes with my card-specific driver (I have an
ET4000), it works fine.

So: I guess you should use a card-specific driver if you can. 
Otherwise, it seems you get to live with 320x200.
-- 

Nate Eldredge
nate AT cartsys DOT com

- Raw text -