---------------------- GLSetup 1.0.0.118 Beta ---------------------- GLSetup currently includes drivers for the following chipsets: 3Dfx Voodoo, Voodoo2, Voodoo Rush, Banshee, Voodoo3, Voodoo3 3500TV, Voodoo4, and Voodoo5 3Dlabs Permedia 2 and Permedia 3 ATI Rage 128, Rage 128 Pro, Rage Fury MAXX, Rage Pro, Radeon Intel i740, i810, and i815 Matrox G200, G400, and G450 NVidia Riva 128/128ZX and Riva TNT/TNT2/GeForce1&2/Quadro1&2 Rendition Verite 2200 S3 Savage3D, Savage4, and Savage2000 Please visit http://www.glsetup.com for information on other chipsets. --------------------- Known Bugs and Issues --------------------- Both GLSetup itself and most of the drivers it installs are BETA quality. This means they have bugs and you should proceed with care. Because GLSetup is a BETA product, it sometimes screws up. You are running GLSetup at your own risk, so please read this bug list to figure out how it might screw up on your system. If GLSetup fails to work properly for you, please follow the instructions in the Bug Reporting section of this document. You can find a more up-to-date list of issues for GLSetup and each display card at http://www.glsetup.com. - We're trying to track down a problem where after installing GLSetup, you cannot switch out of 640x480 mode. Sometimes reinstalling the monitor drivers via the display control panel solves the problem. Uninstalling GLSetup also fixes the problem. If you have this problem, and can reproduce it repeatedly (in other words, you install, have the problem, uninstall, it goes away, reinstall, it occurs again, etc.), PLEASE send a bug report (see below) and mention this clearly. It would really help us track down the problem. - It is very important that you have the latest drivers for your motherboard installed before you run GLSetup. This is important for all users, but it is especially true for AMD CPU owners with ATI cards (ATI Rage MAXX cards will not even boot with the latest display drivers if the motherboard drivers are not up to date, and you'll have to reboot in Safe Mode and uninstall them). Please update your motherboard drivers before continuing. The webpage for your computer manufacturer should be able to point you in the right direction to upgrade the motherboard drivers. - WindowsMe users should be aware that the Savage4 driver (and possibly other drivers in GLSetup) has not be signed for WinMe. When GLSetup installs the driver, you will be prompted with a dialog by WinMe. To force the install, you must select the advanced button and then ask to be warned about unsigned drivers. Click ok, select yes to install the driver, and then proceed with the install as usual. - The ATI Rage 128 drivers included in this build of GLSetup may not detect some Rage 128 chipsets. Please file a GLBug bug report if you run into this problem. - The ATI Rage 128 Pro drivers on Windows95 will display a blue screen error in ATI2VXAA when booting. Ignoring this error seems to work fine in our tests. ATI has stopped testing their drivers on Windows95 and only tests on Windows98 and newer OSes, but GLSetup continues to test the drivers on Windows95. - The 3dfx Voodoo Banshee drivers can display corrupted text when running in 32bit mode. - The final screen of a game or a blank screen may continue to be displayed when exiting games running on 3dfx Voodoo3 drivers, but the computer will be active and the mouse will function. Expert computer users can attept to reset the display while its obscured by this final game screen by launching a command prompt using Start|Run, typing "command", and then forcing the DOS box to full-screen using alt-enter. This will reset the video card. - Many drivers are not localized and will install in English even on non-English systems. - ATI Rage Fury MAXX owners are presented with the MAXX drivers, and two Rage128 drivers. Select the MAXX drivers, DO NOT SELECT THE RAGE 128 DRIVERS IF YOU HAVE A MAXX. This is a bug in GLSetup's detection code and it will be fixed shortly. - Make sure your NVidia TNT video card bios is up-to-date. - 3dfx Voodoo3 3500TV owners are presented with a choice of the 3500TV drivers or the default Voodoo3 reference drivers. Unless you're having problems, it's recommended that you use the 3500TV drivers. - The NVidia TNT and GeForce driver control panels on Win95 do not load the "Additional Properties" pages correctly. - The installation progress bars and time estimates are usually completely wrong, especially on the web-based install. - Your system should have DirectX 7 or higher installed before running GLSetup. Most of the drivers require DX7 to function properly. It's not clear whether installing DX7 after running GLSetup is sufficient, but it seems to usually work in our tests. To be on the safe side, install DX7 before running GLSetup. GLSetup cannot currently detect whether you have DX7 installed before running. We have not tested this build with DX8. Please file a bug report if you have problems. - Sometimes GLSetup will not detect a supported chipset if the previous drivers were installed incorrectly (or you told Windows not to install drivers when it detected the card). In this case, open the Device Manager by right clicking on My Computer, select Properties, go to Device Manager, and delete the device. Reboot. If the display device is a primary display device (the one on which your desktop runs), select Standard VGA. Finally, run GLSetup again. - GLSetup may occasionally install older drivers than the ones you have installed. If this happens and you did not choose to do this by forcing GLSetup to install the drivers, please file a bug report. - Uninstall has not been thoroughly tested. Sometimes it doesn't work. Sometimes it uninstalls more than expected. Sometimes it doesn't ask to reboot when it should. See the section below on how to report bugs the "right way." - Running GLSetup on systems with multiple monitors has not been tested. Microsoft currently does not support OpenGL hardware acceleration on multiple monitor systems. Email them and encourage them to fix this. - Changing the install directory has not been thoroughly tested. The install directory can be set to bad places, like the system directory and the root. Don't do this. - Although a driver for a specific chip set may be supported by GLSetup, this does not mean all boards with that chipset are supported. For example, GLSetup will not detect a Real3D Starfighter PCI card, even though the Intel i740 drivers are included in GLSetup. The Starfighter PCI is incompatible with the Intel reference drivers. We're always working to include more drivers in GLSetup, so check http://www.glsetup.com for updates. - The Intel i740 drivers need the usbsupp.exe Universal Serial Bus drivers installed to operate properly on Windows95. This program should be on your Win95 install disk if you received Win95 OSR2 with your computer. - The ATI drivers create a C:\ATI directory without asking for permission. - 3Dfx Voodoo2 SLI is detected as two Voodoo2 cards. Pick one and the install should work properly. Report a bug if it fails. - Installing DX6 on a 3Dfx Voodoo1 on Win95 appears to hose the card's drivers, and GLSetup will not detect the card, as mentioned above. Removing the device in the Device Manager, and then running GLSetup fixes this problem. - We have experienced hardware hangs in some graphically intensive games on certain NVidia Riva TNT2, 3Dfx Voodoo3, and S3 Savage3D boards. We believe this is a problem with these boards and Intel LX chipsets. There have also been problems reported on some AMD ALI chipsets. - The 3Dlabs Permedia 3 drivers appear to be broken when texturing on Win95OSR2. They work on Win98. - The Rendition Verite 2200 drivers have an anomalous flicker problem while running some games. - If you have multiple supported video cards in your system, GLSetup will only allow you to install one driver per run. - GLSetup only runs on Win9x. It does not run on WinNT. Please see http://www.glsetup.com for information on OpenGL drivers for other operating systems.