Message-ID:	<002b01bf9765$f56521c0$aedd93c3@ant>
From:	"Anthony Graham" <E_MAIL_Anthony AT FonzyCo DOT co DOT uk>
To:	<djgpp AT delorie DOT com>
References:	<8bj6p1$1tp$1 AT gxsn DOT com> <200003261047 DOT PAA03897 AT midpec DOT com>
Subject:	Re: A VESA Question
Date:	Sun, 26 Mar 2000 20:57:54 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.00.2919.6600
Disposition-Notification-To:	"Anthony Graham" <E_MAIL_Anthony AT FonzyCo DOT co DOT uk>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6600
Reply-To:	djgpp AT delorie DOT com

thanks anyway, the reason was the code i'm doing is for a school project and
i really should understand what it's doing and i dont get how dpmi works

- Anthony
----- Original Message -----
From: "Prashant TR" <tr AT midpec DOT com>
Newsgroups: comp.os.msdos.djgpp
To: <djgpp AT delorie DOT com>
Sent: Sunday, March 26, 2000 10:47 AM
Subject: Re: A VESA Question


> "Anthony Graham" <News_Anthony AT Fonzyco DOT co DOT uk> proclaimed:
>
> > Is it possible to get Vesa mode info without DMPI or far pointers? I'm
> > trying not to use these.
>
> You have to use this. You have no other choice. Anyway, I don't understand
why
> you need to do such a thing. What prevents you from using far pointers? As
> far as DPMI is concerned, you can't avoid that. It's always there, at
least,
> as long as your program is executing.
>
> > I went on the dj delorie site and got their vesa
> > source and tried to convert it (stop using dpmi and use int386/int386x)
>
> You shouldn't use int386. It's *not* for calling normal (real mode)
interrupts.
> Are you talking of a 16-bit source code that can give you this info?

- Raw text -