home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!wupost!gumby!destroyer!ncar!uchinews!ellis!sip1
- From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
- Subject: Trident 16-Bit Driver Tip
- Message-ID: <1992Dec12.234642.15736@midway.uchicago.edu>
- Sender: news@uchinews.uchicago.edu (News System)
- Reply-To: sip1@midway.uchicago.edu
- Organization: Dept. of Econ., Univ. of Chicago
- Date: Sat, 12 Dec 1992 23:46:42 GMT
- Lines: 33
-
- On my system (and perhaps yours), the 800x600 16 color Trident 16-bit
- driver works quite well except for one strange problem. Occasionally
- a text window (like the OS/2 command line window) will open
- incorrectly such that the contents of the window are offset about one
- character to the left of the window border. Hence, when you type, you
- can't see the first character on the left of each line. Maximizing
- the window cures the problem, but it is a minor annoyance.
-
- I've found, however, that the command:
-
- MODE CO80,25
-
- resets the window and redraws it properly, to avoid the problem. You
- can use this command instead of maximizing the window. To automate
- the procedure, you can run the command by putting:
-
- /K MODE CO80,25
-
- in the optional parameters section of your OS/2 Windows program object
- (on the first page of the notebook settings).
-
- I haven't tried it, but it may be possible to change the SET OS2_SHELL
- line in CONFIG.SYS to achieve the same effect, so that the line reads:
-
- SET OS2_SHELL=C:\OS2\CMD.EXE /K C:\OS2\MODE CO80,25
-
- I would be interested in any other ideas on this point.
-
- --
- Timothy F. Sipples | Read the OS/2 FAQ List 2.0h, available from
- sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/info
- Dept. of Econ., Univ. | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
- of Chicago, 60637 | [Read the List, THEN post to ONE OS/2 newsgroup.]
-