From: jbs30000 AT aol DOT com (Joel)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Inline assembly error
Date: 10 Aug 2003 19:05:24 -0700
Organization: http://groups.google.com/
Lines: 16
Message-ID: <84e4e2a9.0308101805.296421cb@posting.google.com>
References: <84e4e2a9 DOT 0308072140 DOT 47872db2 AT posting DOT google DOT com> <84e4e2a9 DOT 0308082024 DOT 59e5816b AT posting DOT google DOT com> <3f34b5c7$0$164$cc7c7865 AT news DOT luth DOT se>
NNTP-Posting-Host: 172.140.101.103
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1060567524 9404 127.0.0.1 (11 Aug 2003 02:05:24 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: 11 Aug 2003 02:05:24 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Thanks.  Changing the "C" to "c" fixed the problem.  The reason that I
obsessed over the first line of inline code was because that's what
rhide was highlighting every time it showed the error.
I should know by now that sometimes the wrong line will get
highlighted when an error occurs, but this time it seem that I forget.
Thanks for your help.
Oh, and as for why I'm placing ax into es, it's because there is no
way to do a "%es" (TableSeg) so I placed TableSeg into ax, then placed
ax into ex.  Although thinking about it, I should do a "m" (TableSeg)
"movw %w1, %%es" or something like that.
And I cal it TableSeg because I have this version and the real mode
version of this routine, and a function pointer that points to this,
if I can get the protected mode pointers OK, or the real mode, if not.
 And so, to keep everything the same, the real mode, protected mode,
and function pointer argment names are all the same, and they're bases
on the real mode function.