Message-ID: <3870F41C.88A83E92@connection.com>
Date: Mon, 03 Jan 2000 14:10:22 -0500
From: sam <samirw AT connection DOT com>
X-Mailer: Mozilla 4.6 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro, VESA - help
References: <fyoofqnexgrpubet DOT fnr9ng0 DOT pminews AT nntp DOT generation DOT net> <38709A68 DOT C56D21EE AT maths DOT unine DOT ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: pm1-133.connection.com
X-Trace: 3 Jan 2000 14:24:53 -0500, pm1-133.connection.com
Lines: 28
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Gautier wrote:

> > (...) This simply indicates that the entire VRAM is
> > one big bank. However, when I tried putting this to practice, I still ran
> > into multiple banks (trying to write past a certain range of pixels showed
> > the bank being 'cut off') ..
>
> In fact, you are trying to access the entire video memory in one block,
> but without VESA 2 ?... Why not using VESA 2 (emulated if needed) and the
> linear frame access, getting rid of the banks ?
>
> --
> Gautier
>
> _____\\________________\_______\_________
> http://members.xoom.com/gdemont/gsoft.htm

Just my bit of knowledge. When VESA 1.2 was around that was when manufacturers (
i guess ) started implementing support for  linear buffers.
So while VESA had no software support for it ( or very little ) the hardware
was capable of this. My windows 3.1 driver for the Trident 9400 was doing
this and virtual screen (too bad I cant get a Win95 driver that does this.)

Anyone out there have a Trident 9400 with 2 Megs and can tell me what chips
to populate the second Meg with?