Last updade: 1999-11-30

Installation


Hardware installation

Be very precise and careful while installing your MGA board. While it is very hard to destroy the board, many people are very surprised when they find out that incorrect installation was a source of many problems they attributed to software. I service PCs since 1986, and often face this kind of problems.

Motherboard's BIOS Setup parameters

Before you start installing the driver, it may be a good idea to review and correct some setting in your computer's BIOS Setup. The following options may influence the operation of your graphics controller.
Video BIOS shadow
This option is very cryptic in contemporary BIOSes, since the video BIOS is (and must be) always shadowed, otherwise the video card would be unable to initialize. I believe that this option means something very different than it should mean. Keep it Enabled
Video BIOS cacheable
This influences the operation of DOS programs, and is irrelevant for Windows applications. Keep it Enabled.
Video RAM cacheable
Another cryptic option with false name. The video RAM is never cached, so the string "Enabled" probably means that Write Combining (not caching) is enabled for accesses to video RAM. Keep it Enabled. If the system is not stable, try Disabling it to check if it solves the problem. In some BIOSes the option has the proper values (saying WC enabled/disabled). Set it to Disabled for safety, Enabled for normal operation.
Read around write
This option, present in MVP3-based motherboards may strongly influence the operation of graphics card. G200 with older drivers required it to be Disabled, which is definitely the safe setting. I have no problems running my G400 with Enabled setting.
Cache pipeline
Same remarks as above
Assign IRQ to VGA
Must be set to Enabled if you want to run any 3D applications.
PCI IRQ activated by
Must be set to Level for correct operation. Many cards will not work at all if set to Edge.
Init primary display
Totally irrelevant if you have only one graphics controller. Any single controller (AGP or PCI) will work OK with any setting. Set it if you have two graphics cards to select the "primary" one.
AGP aperture size
Another cryptic option. In theory, it should be set to approx. half of system RAM size. Many experiences show that the real size of AGP aperture in most systems is set half of the value set in this option. Thus I recommend setting it to full system RAM size. Note that some people report that on some motherboard it is necessary to set it to 256 MBytes regardless of the amount of RAM installed.
If you have anything to add here, feel free to contact me.

MGA BIOS Upgrade - basic routine

New BIOS releases fix some incompatibilities between motherboard and MGA card. It is a good idea to upgrade the BIOS, especially if you encounter some instability. To upgrade the BIOS follow the steps below:


Software installation

AGP VGA checklist

As AGP is a descendant of PCI, any AGP board may be safely used as a fast PCI board in AGP slot. This means that even old software (like old version of Windows95) will run on AGP board, but it will not use the new AGP capabilities.
To get the most of AGP, one needs:

Running AGP VGA board on MVP3 motherboards

Things needed: The routine: If you get and install all of these, your Matrox card is supposed to run. If everything works, Final Reality should recognize AGP and run flawlessly. Note: "SHOULD" is the keyword here...


Dual monitor support using two VGA cards under Win98

In theory, any two PCI/AGP VGA cards should work together under Win98. The real problem may occur with similar cards running together.
It may be safely assumed that any Matrox card will work together with any non-Matrox card.
It may also be asumed that any two Matrox cards based on identical chips will work together with any contemporary driver starting from v4.1x.
For Matrox fans it may be interesting to run two different Matrox cards together. A typical case involves two cards from different generations, like Millenium or Mystique with G200. This is possible with the careful selection of drivers. It can be done in two ways:
The same driver is used for both cards
This has a disadvantage of using an old driver for a new card. The best choice here should be version 4.21 (.ZIP, not .EXE version, cause the latter will not install on non-G200 board).
Two cards use different driver
This is the only way to exploit the G200 to its limits. G200 runs under G200-specific driver, version 4.50 or above, while the other cards works with driver version 4.21 or below. This is possible due to the fact that new G200-specific drivers use file names different than unified drivers. My setup worked with Mystique 170 under 4.21 (.ZIP version) and Millenium G200 under 4.51.
Personally I tried Matrox Mystique 170 with nVidia Riva 128 and Mystique with Millenium G200. Both configurations worked OK.