#VESA Interface . . . NOT
3 messages in this thread
Thank you to Martin and GreG for your suggestions on my non-VESA displaying
Pentium.
Martin asked what video board…Cirrus – GD610/20.
GreG suggested getting appropriate drivers. I took a look at my config.sys and
didn't see anything that looked like a VESA driver being called up. Looked for
DOS drivers in C: but haven't found them yet. Verily as we e-mail, found a
directory of windrvs. but the name suggests I might be barking down the wrong
"tree". Anyhow, there are about 75 drivers in it, none with a name hinting at
VESA. Have sent e-mail to manufacture requesting VESA driver and will get the
universal driver if necessary.
Thanks for the suggestions, gents. Will let you know how things go.
Denny
Please let me know if you get a Vesa driver that works with Cirrus and Imagine.
I also have the Cirrus chipset on a laptop and have tried different Vesa
drivers from different software authors that claim to meet the Vesa spec.
Unfortunately the spec is subject to interpretation and although one of the
authors software recognizes my chipset correctly and uses and is able to set
the various resolutions, Imagine uses the other authors routines which don't
recognize the same capabilities. The Universal VBE is the one that doesn't
recongize the Cirrus chipset and is what I believe Impulse/Imagine uses.
Thanks.
Ijust mounted the driver GreG T. suggested for my cirrus chips. It appears to
work on my cirrus 54xx chips. If you're keeping score, you'll notice my chip
numbers changed. QEMM disagrees with Norton and the VESA driver. Majority
says 54xx. Minority says 610/20.
The forum that had it was GRAPHSUP. Sorry I don't know which library had it
'cause I had CSNAV check every one that had a name hinting that it might. GreG
belived the name was UVBE50.ZIP. Real close for memory. The driver package
was UNIVBE.ZIP, and the actual driver was UNIVBE version 5.0.
Mounting it was a piece of cake. The intaller in the package did the job. No
Imagine 3.2 comes up w/o the big error message and at least the PC400 displays
properly in quick render.
Since the installer put its driver at the top of my autoexec.bat file,
theoretically, it may have impacted something later on the list. I haven't
tested my whole system, just my Im 3.2 defaults. But they do work.
BTW, UNIVBE 5.0 includes an energy saving screen saver. And UNIVBE is
shareware. We have 21 days to test. By which time we need to shut it off or
order a serialed license for at least $28. All explained in the docs and
onscreen during boot!