Category : Communication (modem) tools and utilities
Archive   : GIFLK111.ZIP
Filename : VESA.TXT

 
Output of file : VESA.TXT contained in archive : GIFLK111.ZIP

A number of VESA video drivers are packed into the self-extracting file
VESA.EXE. Type "VESA" at the DOS command line to unpack the drivers into
their own directories.

These directories contain terminate and stay resident (TSR) versions of
most Super VGA card's VESA BIOS Extensions implementations. The TSRs
have been placed in the public domain by the various graphics card
manufacturers. They may be freely copied and distributed.

There is no way for us to insure that these are the latest drivers from
the various graphic card companies. We take no responsibility for the
drivers and make absolutely no warranties as to their use. The safest
option is to obtain the appropriate Vesa driver directly from your
graphics card manufacturer.

We will say that if you have a HiColor graphics card, then the Tseng
driver is one that you might try after trying the driver for your
specific graphics card. If the video chips for your graphics card were
made by Chips & Technologies, then you may want to try the driver
provided by Chips & Technologies in addition to a driver which was made
for your graphics card. If your video card is based on the Western
Digital 24 bit chipset, you may want to try the vesa driver from Western
Digital in DIAMOND2.ZIP which supports the Diamond 24X.

Once you have find the driver for your adapter, simply put it into your
AUTOEXEC.BAT and all VESA-aware programs will be benefit from it.

This collection of graphics card VESA drivers is provided without charge
or support, and is only provided for your convenience. NO WARRANTIES ARE
APPLICABLE.



  3 Responses to “Category : Communication (modem) tools and utilities
Archive   : GIFLK111.ZIP
Filename : VESA.TXT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/