Date: Wed, 20 Oct 1999 13:08:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Gisle Vanem <giva AT bryggen DOT bgnett DOT no>
cc: djgpp AT delorie DOT com
Subject: Re: far call
In-Reply-To: <Pine.UW2.3.95.991019185402.20452B-100000@bryggen.bgnett.no>
Message-ID: <Pine.SUN.3.91.991020130833.22660E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 19 Oct 1999, Gisle Vanem wrote:

> >> Maybe I need to modify the selector for 'execute' ? (don't think so)
> >
> > I think you do need that.  In which case you will have to define two
> > selectors: one for data, another for code, with the same base address
> > and limit, but different descriptors.  (DJGPP does exactly that for CS
> > and DS, btw.)
>  
> Bingo, changing the access-reight (ORing with 8) did the trick.
> A "fresh" descriptor seems to only have Read/Write access.

The DPMI spec says that an LDT descriptor is by default set to be for
data, not for code segments.  So this is expected.