home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Help! OS/2 full screen sessions video mangled.
- Message-ID: <1993Jan21.195654.20726@njitgw.njit.edu>
- Date: 21 Jan 93 19:56:54 GMT
- References: <1jliv7$655@agate.berkeley.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 27
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1jliv7$655@agate.berkeley.edu> dmillar@ocf.berkeley.edu (Derek Millar) writes:
- >It turns out to have been a problem with the vertical refresh rate:
- >The new monitor supports 640x480 at 72Hz, so that's what I had my video
- >card set to. However, the OS/2 driver screws up fullscreen OS/2
- >sessions if the vertical refresh at 640x480 is greater than 60Hz.
-
- Interesting. The only explanation I can come up with is timing
- register changes. In theory, you're only supposed to alter video
- registers (like the mode and palette, etc) during blanking (horizontal
- or vertical) intervals. If you increase the frequency too high, then
- the system doesn't have enough time to set all the registers it wants
- to during the interval and the display messes up. Since VGA (640x480)
- is an IBM mode, IBM may be critically timing their processing to a
- PS/2's refresh rate.
-
- >Oddly, the OS/2 driver works better at 72Hz at 800x600.
-
- The 800x600 driver is probably looser with the timing specifications,
- so it can fit all of its register changes in during the blanking
- interval at 72Hz. Or the sVGA driver knows of a better way to get at
- the registers on your model card that doesn't require waiting for
- blanking intervals.
- --
- |) David Charlap | .signature confiscated by FBI due to
- /|_ dic5340@hertz.njit.edu | an ongoing investigation into the
- ((|,) | source of these .signature virusses
- ~|~
-