From:	afn03257 AT freenet3 DOT afn DOT org (Daniel P Hudson)
Newsgroups:	comp.os.msdos.djgpp
Subject:	RHIDE hates mieses to pieces
Date:	24 Jan 1997 01:55:49 GMT
Lines:	24
Message-ID:	<5c94r5$k2v@huron.eel.ufl.edu>
NNTP-Posting-Host:	freenet3.afn.org
NNTP-Posting-User:	afn03257
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Ignoring the talk about the RHIDE 1.1 mouse bug, I downloaded and
installed, and naturally I found it. For those who don't know the mouse
actually works, but the cursor is hidden. moving the mouse up and then
holding the buttn down will bring up a menu, you just can't tell which
one at first. I've also noticed after returning to command.com, the
cursor is hidden. I have a 6 byte com file to clear that up,
unfortunately, my idea to patch the mouse temporarily didn't work.

Nonetheless, I may know why the mouse doesn't work so hot, Robert.
You've called hide() more than show(). I am not familiar with TV
or whatever the code belongs too, but the MS mouse drivers keep a count
of the number of times a mouse is shown or hid and it will not return
until the number of calls to show is one more than the number of calls
to hide. I can only assume this is the same with the driver that's being
used here if it isn't MS's. Now assuming show and hide are indeed the
corresponding int 0x33 services, you probably called hide instead of
reset somewhere. I believe the reset is called when the
new text modes are set and that is why it will work after this.
I must confess, I'm a little lost stumbling though your code at the
moment, but a quick find.bat file only turned up a few lines with the
word mouse, and none of them look suspicious to me, YET. You may
have already figured this out, but I though if you hadn't it would
speed up your debugging.

- Raw text -