From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Problems adressing memory variable
Date:	Sat, 15 Mar 2003 11:43:57 CST
Organization:	Rice University, Houston TX
Lines:	9
Message-ID:	<3e73665d.sandmann@clio.rice.edu>
References:	<G3wca.1706$z_3 DOT 763310 AT news1 DOT news DOT adelphia DOT net> <200303150305 DOT h2F35DG11549 AT envy DOT delorie DOT com> <L8yca.1778$z_3 DOT 804270 AT news1 DOT news DOT adelphia DOT net>
NNTP-Posting-Host:	clio.rice.edu
X-Trace:	joe.rice.edu 1047750219 5723 128.42.105.3 (15 Mar 2003 17:43:39 GMT)
X-Complaints-To:	abuse AT rice DOT edu
NNTP-Posting-Date:	15 Mar 2003 17:43:39 GMT
X-NewsEditor:	ED-1.5.9
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> Ok, I think I've gotten most of the bugs worked out by now.  But the silly
> thing still won't work...  What am I doing wrong this time?

>     output.x.ss = __tb & 0x0f;

The interrupt call uses ES:BP, not SS:BP

Not sure if that fixes it, but I know you rarely set SS to a __dpmi_int 
call.

- Raw text -