home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.os2.misc:35829 comp.os.os2:433 comp.os.os2.apps:8015
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!ogicse!news.u.washington.edu!hardy.u.washington.edu!rene
- From: rene@hardy.u.washington.edu (Rene Magritte)
- Newsgroups: comp.os.os2.misc,comp.os.os2,comp.os.os2.apps
- Subject: **SOLVED** the "HELP HELP HELP" Video problem
- Summary: Problem with Service pack solved
- Keywords: SOVLED@
- Message-ID: <1992Nov8.234601.29962@u.washington.edu>
- Date: 8 Nov 92 23:46:01 GMT
- Article-I.D.: u.1992Nov8.234601.29962
- Sender: news@u.washington.edu (USENET News System)
- Organization: University of Washington
- Lines: 24
-
-
-
-
- Well, with a little intuition and a lot of luck I solved the
- video problem I was having under OS/2 + CSD. Thanks to the many of
- you that wrote me to help, but my solution ended up being different
- than any of the ones people suggested to me. Many people suggested
- various ways to run the "vmode" utility before/during OS/2 bootup.
- The problem was that it seemed that the OS/2 desktop was being drawn
- in a non-interlaced, too-high-refresh-rate-for-my-monitor mode. I
- could get to a fullscreen session and run the vmode utility, but when
- I switched windows to the desktop, everthing would be screwed up
- again.
- Desperate, I took a look at the file that SVGA had produced
- (name escapes me right now). I scrolled through the various video
- modes that OS/2 had tested, thankful for the human readable format. I
- noticed the Interlace=1 command next to the mode I was interested in.
- Hmmmmm...... I scrolled down and noticed that the 1024x768 mode said
- Interlace =0. Crossing my fingers, I changed the 800x600x256 mode to
- Interlace=0. I rebooted, hoping I wouldn't fry my card or
- something, and....success! Everything is hunky dory now.
-
- If I could just get my damn modem to work...where is my
- com.sys?
-