home *** CD-ROM | disk | FTP | other *** search
- Microsoft WinG version 1.0
- --------------------------
- WinG version 1.0 provides fast picture-to-screen performance
- under Windows 3.1, Windows for Workgroups 3.11, Windows 95, and
- Windows NT version 3.5. WinG will not run on Windows NT version
- 3.1 or on earlier versions of Windows.
-
- WinG requires a 386 or better processor to run. WinG will not run
- on a 286.
-
- Updated information on WinG is available on CompuServe in the WINMM
- forum and on ftp.microsoft.com.
-
- Suggestion
- ----------
- If your current display driver fails to work properly, try using
- the Windows default Super VGA (640 x 480, 256 colors) driver
- with NO manufacturers specific name. This driver is also available
- on CompuServe in the Microsoft Software Library.
-
- Driver-Specific Problems
- ------------------------
- WinG depends on Windows display drivers written by independent
- hardware manufacturers for much of its speed. Bugs or performance
- problems in third-party display drivers may cause problems in WinG.
- In many cases, the video card manufacturer has already fixed the bug,
- and upgrading your display driver will often clear away problems.
-
- There are some specific "bugs" in display drivers of which you should
- be aware. The list below is not intended to slight the manufacturer
- of any particular card or driver.
-
- A list of stress-tested configurations is available on the CompuServe
- WINMM forum and ftp.microsoft.com.
-
- Some names in this list are trademarks of the respective
- manufacturer.
-
- - Early drivers for Diamond Viper cards included a "Power Palette"
- option that is no longer supported by Diamond. They recommend that
- you upgrade your drivers if you have this option. WinG may be
- slower when power palette is enabled.
-
- - IBM no longer supports the IBM ThinkPad 720c. There are some
- problems using WinG with the ThinkPad 720c display drivers.
-
- - Cirrus drivers before version 1.43 have many known bugs which
- have been fixed in the more recent drivers. Be sure to upgrade your
- drivers if you are still running with this version.
-
- - Some ATI drivers offer a "Crystal Fonts" option. Turning Crystal
- Fonts on in 8-bit modes sets up a non-palettized driver that can
- slow WinG significantly.
-
- - The ATI mach8 Radical drivers cause a number of problems in both
- WinG and in Windows with some versions of the ATI chipset. Be
- aware.
-
- - The ATI VGA Wonder drivers (W31-*.drv) will crash during a call to
- StretchDIBits in the profiler. Users can run the SVGA256.DRV driver
- that shipped with Windows.
-
- - Many miro Crystal drivers have problems with StretchDIBits, so they
- crash during profiling.
-
- - Early ATI Mach 32 PCI cards have a hardware timing problem and will
- hang while blting. ATI will replace these cards for no cost.
-
- - WinG is incompatible with the #9GXE "TurboCopy" mode. Use the
- #9 control panel to disable TurboCopy (it is off by default).
-
- - WinG uses a GetPixel to synchronize with display hardware when
- writing directly to the screen. The ATI Mach 32 driver's GetPixel
- does not work properly, so it is possible to use GDI to draw to
- the screen, then use WinG to blt to the screen and have them overwrite
- each other. Be careful mixing GDI drawing commands and WinG blts
- to the display.
-
- - The Orchid mmtllo.drv driver for the Prodesigner IIs has duplicate
- system colors which prevents applications from getting an identity
- palette and greatly reduces the WinG blt speed. A workaround is
- to set SYSPAL_NOSTATIC mode or use standard the Tseng ET4000 drivers
- instead of the mmtllo drivers.
-
-