From: "sl" <junk AT bbs DOT darktech DOT org>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: VESA 1.2, cannot get current video mode!
Date: Mon, 03 Jan 2000 21:53:32 -0500 (EST)
Organization: Posted via Supernews, http://www.supernews.com
Lines: 22
Message-ID: <fyoofqnexgrpubet.fnsip80.pminews@nntp.generation.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000102131522 DOT 6098F-100000 AT is>
X-Complaints-To: newsabuse AT supernews DOT com
X-Newsreader: PMINews 2.00.1205 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

On Sun, 2 Jan 2000 13:18:47 +0200 (IST), Eli Zaretskii wrote:

>I suspect that this is either a bug or an extension specific to the 
>vendor of your SVGA.  Since the Interrupt List says that AH=1 signals an 
>error, and you get AH=80 (is it 80 hex or decimal, btw?), I suggest to 
>try to treat it as successful return, and see whether the rest of the 
>functions work.

	So far all other functions work except this one. Do you happen to
know how Allegro handles this problem? I tried taking a quick-look at it and
haven't been able to find a "get_current_video_mode" function anywhere..

>For more confidence, you could use functions 4F00h and 4F01h, which
>return similar information, and see whether 4F03h is consistent with 
>them.

	I tried just that.. Only 4F03h mishaves .. Does the author of Allegro
read these messages? I'd like to ask him a few questions.

Gili