VESA Interface . . . NOT
01-Mar-95 00:32:14
Sb: #102854-VESA Interface . . . NOT
Fm: Dennis L. Smith 75463,302
To: Bernie Parent 71550,3633
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!