delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/03/26/07:31:40

Date: Sun, 26 Mar 2000 15:47:23 +0500
Message-Id: <200003261047.PAA03897@midpec.com>
From: tr AT midpec DOT com (Prashant TR)
To: djgpp AT delorie DOT com
In-reply-to: <8bj6p1$1tp$1@gxsn.com> (News_Anthony@Fonzyco.co.uk)
Subject: Re: A VESA Question
References: <8bj6p1$1tp$1 AT gxsn DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

"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 -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019