cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1997/03/10/17:12:32

From: Niklas <d95-nlu AT nada DOT kth DOT se>
Newsgroups: comp.os.msdos.djgpp,comp.graphics.algorithms
Subject: Re: VESA 2.0 and NEAR PTR
Date: Mon, 10 Mar 1997 22:02:06 +0100
Organization: Solace Computer Society
Lines: 26
Message-ID: <332476CE.7205@nada.kth.se>
References: <33232BE7 DOT 2F3D AT nada DOT kth DOT se> <3323C8DB DOT 308F AT eps DOT agfa DOT be> <Pine DOT SOL DOT 3 DOT 91N2x DOT 970310110907 DOT 14527B-100000 AT mastermind DOT nada DOT kth DOT se> <3323FDFC DOT 1609 AT idb DOT hist DOT no>
Reply-To: d95-nlu AT nada DOT kth DOT se
NNTP-Posting-Host: sl116.modempool.kth.se
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> The videomode 0x4101 isn't defined according to the SciTech vbe2.0 Core
> infofile, because VESA videomodes are only 14 bits wide:
> 
> ".....the optional VBE mode numbers are 14 bits wide. To initialize a
> VBE mode, the mode number is passed in the BX register to VBE Function
> 02h (Set VBE mode)."
> 
> So what you have to do is to SET the mode 0x0101 with bit 14 enabled
> (that is BX=0x4101), and SEARCH after the mode 0x0101 in the
> VideoModeList.
> Some VESA TSR's are actually storing both 0x0101 and the 0x4101 "mode"
> in the VideoModeList, but according to the (unofficial) specs from
> SciTech, 0x4101 isn't a VideoMode so it should't be located in the
> VideModeList.
> Hope this solved the problem.

> 
> Regards,
> LoveDoorFoxor /Talent
> http://www.idb.hist.no/~jans

I got the mode from GRX 2.0 in djgpp, the program VESAINFO.EXE so I
guess it should work, and the above program enters the mode and says
it's got a LFB..

Niklas

- Raw text -


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