From: "Matthew Conte" <spam AT somebody DOT else>
Newsgroups: comp.os.msdos.djgpp
References: <Pine DOT SUN DOT 3 DOT 91 DOT 981022094732 DOT 2003G-100000 AT is>
Subject: Re: new user - mouse problems
Lines: 26
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Message-ID: <6NHX1.918$H9.138159@proxye1.nycap.rr.com>
Date: Thu, 22 Oct 1998 10:59:34 -0400
NNTP-Posting-Host: 24.92.55.44
X-Complaints-To: abuse AT nycap DOT rr DOT com
X-Trace: proxye1.nycap.rr.com 909068482 24.92.55.44 (Thu, 22 Oct 1998 11:01:22 EDT)
NNTP-Posting-Date: Thu, 22 Oct 1998 11:01:22 EDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii wrote in message ...
>> regs.x.cx and dx are 16-bit registers.
>
>No, they aren't.  See section 18.1 of the FAQ and the `int86' page of
>the library reference for more insight.

Section 18.1 of the FAQ says nothing about the size of the regs.  In
addition, issuing:

    info libc a int86

gives me this:

"Note: The `.x.' branch is a problem generator.  Most code expects the
`.x.' branch to have e.g. "`.x.ax'" members, and that they are 16-bit.
If you know you want 32-bit values, use the `.d.eax' members.  If you
know you want 16-bit values, use the `.w.ax' members.  The `.x.'
members behave according to `#defines', as follows:"

Sure looks to me like the regs are 16-bit, and would explain why the values
returned when you assumed 32-bit integers are garbage.

Later,
Matt.