From: Prashant TR <tr AT midpec DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: How to write protected mode far call in AT&T style
Date: 15 Jun 2000 23:32:29 +0530
Organization: VSNL
Lines: 21
Message-ID: <m3u2eu256y.fsf@midpec.com>
References: <39470e99 AT newsgate DOT hknet DOT com> <200006140615 DOT LAA03124 AT midpec DOT com> <394734f0$1 AT newsgate DOT hknet DOT com> <200006141715 DOT WAA01487 AT www DOT midpec DOT com> <3947F612 DOT 784F2FCC AT phekda DOT freeserve DOT co DOT uk> <3948b53b AT newsgate DOT hknet DOT com>
NNTP-Posting-Host: 203.197.177.161
X-Trace: news.vsnl.net.in 961130058 17325 203.197.177.161 (16 Jun 2000 04:34:18 GMT)
X-Complaints-To: postmaster AT news DOT vsnl DOT net DOT in
NNTP-Posting-Date: 16 Jun 2000 04:34:18 GMT
X-Newsreader: Gnus v5.7/Emacs 20.5
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"Alvin Lau" <alvin_lau AT yahoo DOT com> writes:

> According the definition:
> 
> typedef struct {
>   unsigned long  offset32;
>   unsigned short selector;
> } __dpmi_paddr;
> 
> The offset32 is followed by selector.
> But Prashant TR said "lcall $selector,$offset"
> Should be selector first then offset second.
> So, does "lcall *_oldtimer" still correct ?

What I said does not hold  true in your case. Since the selector and
offset values are stored in the memory, you must use

lcall _oldtimer or
lcall *_oldtimer like Richard Dawe suggested.

Prashant