Mail Archives: djgpp/1998/09/02/01:45:20
From: | Leif <LeifDude AT hotmail DOT com>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Mouse/Int 33h Problems
|
Date: | Tue, 01 Sep 1998 22:36:41 -0700
|
Organization: | NorthWest Nexus Inc.
|
Lines: | 29
|
Message-ID: | <35ECD969.219F@hotmail.com>
|
NNTP-Posting-Host: | blv-pm102-ip24.halcyon.com
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
I dont know whats goin on with my progy. Im writing a program and using
int86() to call mouse functions of INT 33h. Everything was working fine
and dandy(with a couple of exceptions I will describe later) untill I
added a new loop/function in my program. Every time I called this loop
it caused Int33h Function 03h (Get MousePosition) to report falsely. So
I started to debug my new loop/function. I couldnt find out what the
problem was so I took out the insides of my loop. And my problem
remained. The loop now looks something like...
void MyLoop(char *S){
/*
All the junk in my loop inside here...
*/
}
When I call this loop int33h reports mouse position all screwy and VERY
similarly to the way it was reporting when I was getting the mouse junk
coded in the first place.
My problems at first were fixed by loading bx,cx and dx with 0. Even
though int33H only needs ah=0 and al=3. When I didnt load bx-dx with 0
the screwy reports were coming in. These reports look exactly like the
ones im getting now by calling this empty function.
What gives? Have I reached a limit of some kind in GlobalData or Code
Size?
Any thoughts/ideas or help would be appreciated.
P.S. Ive tried various combinations of debugging/optimization switches
when compiling including none at all.
- Raw text -