Yes, it is a UNIVBE 5.1a problem with certain graphics chipsets. I experience it with
my ArkLogic 2000 based video card. It happens only at 640x480. If you absolutely need
VESA 2.0 compliance to run the game (ICR2 doesn't require it, and on a 100MHz Pent.
doesn't really need it, IMHO) you have a few options:
1) Call your video card manufacturer and check to see if there is a newer BIOS
available for your card. If there is, check to see if it is VESA 2.0 compliant.
If so, get it and install it. If you have VESA 2.0 on the board you will never
have to mess with UNIVBE again.
2) Wait for the upcoming UNIVBE 5.2 (6.0?) release and see if it finally addresses
your card properly. Unfortunately I've heard from good sources that even in
the latest developer beta it still doesn't support ArkLogic 2000 chips or
Matrox Millenia Boards correctly....But, Matrox Millenia board owners can
benefit from #1 above because I know Matrox has a VESA 2.0 compliant bios for
their board now.
3) Buy a new board or wait for all games to go Win95 native.
Disabling things like "VBE 2.0" in the UVConfig program are akin to not even
runing UniVBE. If you don't use VBE 2.0 then you do not benefit from 32bit protected
mode (ie 'flat') memory addressing or the linear framebuffer...the two biggest
speed enhancements that VESA 2.0 compliance give you.


































