DOS has some VESA drivers.
ANSI codes can also be supported. In DOS, this does not supported at the main command prompt unless a driver is loaded. The driver that comes with DOS may not be the best option, due to unnecessarily high memory usage. See: ][CyberPillar][: DOS memory for some further info/details.
In Windows 10, support for ANSI is provided by the console. See: Windows 10 ANSI demonstration (version 1). At the moment, the ZIP file is mostly intended as an example of what can be done, so it does not have a bunch of documentation associated with it. TOOGAM's answer to Makerimages's question on colored text discusses this file a bit further. Users of alternate shells, like Take Command, may be able to use such files by doing something like running "CMD /C TYPE OUT.ANS" or "CMD /C ECHO (ANSI Sequence)".
Linux has SVGALib
For 32-bit Windows, common knowledge dictated that video problems were often remedied by installing the latest available version of the video drivers.
If 32-bit drivers are unavailable, 16-bit drivers may work in some cases. However, in some cases they may not work at all, and even if they work somewhat there may be some compatibility loss and most definitely is likely to have substantial performance loss. Therefore, that option may exist but is probably not worthwhile, in most cases. The performance hit is likely to be substantial enough that searching for better drivers is likely to be more worthwhile.
It does appear that Microsoft did distribute these, but they are not on the MSLFiles FTP site like they used to be. The filenames listed first are the ones that appear to be original/official, having reviewed several sites: http://www.isomedia.com/homes/ftp_html/microsoft/index.htm http://benedict.isomedia.com/homes/ftp_html/microsoft/DRIVERS.HTM http://fresh.t-systems-sfr.com/pc/src/microsoft/softlib/WDL.TXT http://www.geocities.com/~budallen/ftplist.html
EGA driver. (Does not contain CGA drivers according to OEMSETUP.INF, despite some claims that it does, claims likely resulting from the presense of files named CGA*) EGA drivers from site 1, EGA drivers from site 2. The following are the same: http://oldfiles.org.uk/powerload/download/ega311.exe http://wejump.ifac.cnr.it/pages/pub/sw/os/w31_util/ega311.exe
Also available from Metropoli files in a EGA311.ZIP. (This is different than the *.EXE file, containing a BBS advertisement, but the files inside are identical to those from EGA311.EXE.) e.g. EGA311.ZIP. ConradsHome.Com Win3x software
The term “Super VGA” (which may commonly be abbrevated down to “SVGA”) often refers to not only the original “Super VGA”, but also higher resolutions. Therefore, cards that claim to support “Super VGA” will often support newer standards like the XGA video mode resolutions. Be sure to check out driver support for “VESA BIOS Extensions” (commonly abbreviated down to “VBE” or just “VESA”) to see if even higher resolutions may be supported.
Q143315 refers to had a URL for the Super VGA (256 colors) driver at ftp://ftp.microsoft.com/softlib/mslfiles/svga.exe although that file is no longer available at that location.
As that file is no longer available at that location, I found the following:
The following are differnet from each other and from above:
Super VGA driver contains 640x480, 800x600, and 1024x768 modes, all in 256 colors, and the latter each having two versions, one for both Large fonts and one for Small fonts.
WIN311.TXT probably refers to this driver when referencing the following: " - 256 Color generic SVGA video driver, which supports TSENG ET4000 chipsets and V7 but not ATI Ultra or S3 chipsets."
Q82734 discusses the SVGAMODE= setting that gets placed in SYSTEM.INI and describes SVGAMODE=106 (to use video mode 6AH) as being “much more pelasing to the eye” with some VESA cards.
Some video cards came with some VESA drivers specific for the card (meaning that they worked with the card and provided support for VESA compatibility). Many video card manufacturers did not include such compatibility with their video card, even if the video card was capable of higher performance with such drivers. SciTech provided a solution for many video cards by providing shareware offerings. See: http://www.scitechsoft.com/ftp/sdd/ and http://www.scitechsoft.com/products/product_download.html and http://www.scitechsoft.com/ftp/snap/dos/ ( SciTech, UniVBE )
VBEmp 9x Project, VBEmp 9x Project, VBEmp 9x Project, all of which replace VBEMP x86 Project Main page (download section) (archived by the Wayback Machine @ Archive.org), Main page (in Russian), download page, Actual drivers zip file Announcement. This has two drivers, one for ATI, 3DFX, Cirrus Logic, TSENG Labs, and the other for nVidia, Riva128, Intel, Trident, Matrox, and S3.
Note that DirectDraw and Hardware/Software Direct3D are not supported yet (as of January 12, 2008), but then again, it was only announced recently (Dec 6, 2007).
Another VBEMP page cites location of VBEmp source code. (This is for ReactOS, and differs from the VBEmp x86 project.)
nVidia drivers for Windows (and also some other operating systems from the RIVA 128 section) was lengthy enough that the material went onto its own page. nVidia drivers for Windows (and others for RIVA 128)
The movie-like "demos" will likely be on a separate page on this site (near Second Reality demo, etc.) (See“nVidia demos” section of “Code-based Demos (that are like movies)”.)