🚀 go-pugleaf

In article <2n0ber$qm3@bach.udel.edu>,
David Robert Downs <drdowns@bach.udel.edu> wrote:
>In article <2mt7s8$4k9@falcon.ccs.uwo.ca>,
[deletion]
>
>  I have a CL-GD5428 VLB with 1 meg of RAM (upgradable to 2 megs).
>
>  I have never had a crash (due to the drivers), but I have some _weird_
>problems that seem to be driver related.  Has anyone else experience any of
>the following?:
>
>  1.	SetRes says "The graphics adapter does not have enough memory to
>  	support the custom display driver.  Previous custom display driver
>  	installation options will be ignored."  Then, only 640 x 480 by 16 is
>  	choosable.  I am running in 1024 x 768 by 256!

  QEMM 7.01 caused some conflict here.  I can't tell you what feature of QEMM
  is was, but I went back to a working HIMEM/EMM386 setup and told 7.01 to
  Optimize that and though nothing seemed to change (ie same regions, stealth
  mode and memory free), the problem went away.

  So, if you get the above problem - check you memory manager first.

>
>  2.	Word for Windows 6.0a fails to show a character or two every now and
>  	again.  They are there, and are visible after doing a Print Preview
>	(which also shows all characters).  This may just be one of the 8,000
>	known bugs... Thanks MS.

  This does appear to be a Word 6 problem (at least others also suspect Word
  more than Cirrus :)

>
>  * These events (1 and 2) take place under BOTH v1.32 and v1.41 drivers. *

  I'll repeat that 1.41 drivers work fine for me (for what it is worth).

>
>  3.	idchip.exe (in DOS) returns varying information.  Originally I got
>	a 5428 chip reported, just now I get:
>
>  The BIOS reports a CL-GD5426 chip.
>  This is a True-Color VGA GUI Accelerator.
>  The BIOS Version Number is 1.48.
>  There is 1M Byte of Display Memory installed.
>  Detected VESA Version 1.2, with support for the following VESA modes:
>  Mode 108:     0 X    0,   Character Mode
>  Mode 1c8:     0 X    0,   Character Mode
>  Mode 1d3:     0 X    0,   Character Mode
>
>	I have also had it report "2M Byte of Display Memory installed."!
>	Also, why do the modes show "0 X 0"?

  Guess what.  It was that same QEMM problem.  IDCHIP.EXE works perfectly now
  that QEMM has fixed itself :)

>
>  The card was sold as "AcerGraph L28".  Any information you can provide is
>  welcomed.  Anyone else have similar problems?

  The answer is yes...  I would like to thank all those who responded (including
  Cirrus support!).  Hopefully many of you can attribute the problems to memory
  managers or similar software/driver setups and get the conflicts resolved.

  I would like to express my satisfaction with the Cirrus based video card I
  have.  I saw a post which basicly said "Choose Diamond over Cirrus" to which
  I respond DON'T!  I pulled my Diamond 24X for the Cirrus because of major
  Diamond driver problems (even on the latest release) as well as timing
  problems in my 486.  As usual, the best card is what works for you, so take
  this with a grain of salt, but for the money a Cirrus card is hard to beat.

  Thanks again.

  David

--
E-mail: drdowns@brahms.udel.edu   | U  | David R. Downs  | Typos & misspellings
          downs@cis.udel.edu      | of | Newark DE 19711 | are my specialties.
       downs@freezer.cns.udel.edu |  D | (302) 837-1969  |
Computer & Information Science ** My opinions don't reflect those of the U of D