Date:	Tue, 18 Mar 2003 07:52:10 +0200
From:	"Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	ken DOT jen AT adelphia DOT net
Message-Id:	<2427-Tue18Mar2003075210+0200-eliz@elta.co.il>
X-Mailer:	emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	djgpp AT delorie DOT com
In-reply-to:	<p%lda.3401$z_3.1643430@news1.news.adelphia.net>
	(ken DOT jen AT adelphia DOT net)
Subject:	Re: How do you know?
References:	<p%lda.3401$z_3 DOT 1643430 AT news1 DOT news DOT adelphia DOT net>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Ken Jenkins" <ken DOT jen AT adelphia DOT net>
> Newsgroups: comp.os.msdos.djgpp
> Date: Mon, 17 Mar 2003 15:40:05 GMT
> 
> How do you tell a real mode assembly function call from a protected mode
> one?

There's no such thing as ``real-mode assembly'' or ``protected-mode
assembly''.  It's just that code that should run in protected mode
must obey some special rules: not to access absolute memory addresses
outside the program's address space, not to load arbitrary values into
segment registers, etc.

> Because the project I am working on calls for mouse input as well as
> the string output function you have helped me with.  The mouse input
> functions have been coded in extended DJGPP assembly and they work.  So I
> know they are not real mode assembly function calls.  So how do you tell?

So what is the actual problem?  Please tell specific details, like
what did you write to output a string, what happens when you run it,
etc.

Chapter 18 of the DJGPP FAQ list might be a useful reading, too.

- Raw text -