OS/2 Professional/OS2PRO194.ISO/os2/info/apars/os2_20/video.txt

Text File | 1992-07-14 | 7.4 KB | 93 lines

PRINT SELECTION FOR APAR - II06061 92/07/14
APAR= II06061  SER=                            DD DOC
COMMON VIDEO PROBLEMS IN OS/2 2.0 - INFO APAR
OS2INFOAPAR
STAT= INTRAN       FESN5NFO000-000  CTID= II0000 ISEV= 4
SB92/06/03  RC          CL          PD           SEV= 4
                       PE=                       TYPE= I
RCOMP= INFOPCLIB    PC LIB INFO ITE RREL= R001
FCOMP=                              PFREL= F     TREL= T
ACTION=             SEC/INT=                     DUP/
USPTF=              PDPTF=                       DUPS 0
DW92/06/03  RT          SC          FT
RE          PT          UP          LP
PV          AP          EN          FL
LC92/06/23  RU92/06/03
                             CUST INST LVL/SU=
FAILING MODULE=              FAILING LVL/SU=
SYSROUTE OF:          RET APAR=             PS=
COMP OPER ENV=


SYSRES=      SYSIN=      SYSOUT=      CPU=             RE-IPL=
OPTYPE=                 SPECIAL ACTIVITY=          REGRESSION=
PRE-SCREEN NO.=          RSCP= RS000
ERROR DESCRIPTION:
KEYWORDS: OS2INFOAPAR OS2VIDEO

1) Video goes out of synch when switching from DOS full screen
   or WINOS/2 full screen to desktop.
   This is usually caused by Tseng ET4000 chips in the video
   controller (batch TC6059AF or higher only!).  If the customer
   has these chips in his video board, send the fix for APAR
   PJ03677.
2) SYS3176 error when starting a DOS session.
   Try setting HW_ROM_TO_RAM to ON for each session that is
   having the problem.  Also try changing DOS_RMSIZE to 624
   instead of 640.  If this does not work, the VSVGA.SYS fix
   from IBM might resolve the problem.
3) ATI 8514 Ultra or Graphics Ultra locks with white screen on
   bootup.
   The older ATI ROM chips return an incorrect monitor ID when
   queried by OS/2.  Have customer call ATI at 416-756-0711 to
   obtain an update.  Remember, these boards MUST be set up as
   an 8514 PRIMARY display and the statement
         DEVICE= OS2 MDOS VVGA.SYS
   MUST be changed to
         DEVICE= OS2 MDOS VSVGA.SYS
4) C0000005 error on bootup.
   If the customer has Western Digital chips (C30 or C31), with
   1MB memory, send the fix for APAR PJ03721.
   If not, remove the SVGA info from the CONFIG.SYS file.  Note
   that this will limit the user to VGA only. Change
       SET VIO_VGA=DEVICE(BVHVGA, BVHSVGA)
       DEVICE=C: OS2 MDOS VSVGA.SYS
   to
       SET VIO_VGA=DEVICE(BVHVGA)
       DEVICE=C: OS2 MDOS VVGA.SYS
5) Trident video problems:  If the user is experiencing
problems with super VGA on Trident based video boards,
they will need to call Trident (not IBM) for the proper
SVGA driver.  If they have problems with the driver that
Trident sends them, they need to call Trident, not IBM.
IBM only supports VGA mode on Trident boards with 8900 or
9000 chipsets.  The 8800 chipset is not currently supported
nor do I believe that it will be.
6) Dell computer Video problems.  Dell's 486/50 uses a
   Western Digital 90C30 chip.  Our standard BVCHSVGA.DLL
   fix should help.  Other models (325SX, 325, NL25, etc.)
   do NOT use this chip and this fix DOES NOT apply.
   Dell uses a customized Phoenix BIOS.  Here are a few
   CMOS settings that have been known to help.  Use
   CTRL-ALT-ENTER to access CMOS setup:
   FAST_VIDEO                  OFF if sync problems
   FAST_VIDEO_BIOS (shadowing) OFF if problems
   BIOS_CACHING                OFFif problems
   COMPATIBILITY_SPEED         ON for faster Mhz machines
7) Errors loading video drivers on bootup.  The selective
   install utility sometimes will add the same device driver
   statement more than once to the CONFIG.SYS file.  This will
   result in an error message every time the user boots up.
   The system will function properly and upon investigation
   you will find that driver file DOES exist in the proper
   directory.  It is simply trying to load the driver twice
   during bootup, the second attempt will fail.  Remove the
   duplicate DEVICE= statement from the CONFIG.SYS.
LOCAL FIX: