OSHTHANG - INTERMITTENT HANGS RUNNING OS/2 2.X
10/19/94

================================================================
        INTERMITTENT HANGS RUNNING OS/2 2.X
================================================================

Please Read Entire Document for Full Explanation of Procedures
----------------------------------------------------------------

Intermittent hangs have various causes.  Review the
following information to help determine where the system is
failing.

RESOLUTION:

A.  If the system only hangs when running a DOS or
    WINDOWS program, it is probably an application error.

    1. If you are running an application from an icon, does
       the system hang if you run it from the command prompt?
       If so, the icon may be corrupt.  Delete the icon and
       remigrate it or create it from the program template.

    2. Does pressing Ctrl+Esc get out of the hang?  If not,
       can you press Ctrl+Alt+Del to restart the system, or
       do you have to turn the system off?   If pressing
       Ctrl+Esc gets out of the hang, it is an application
       hang contact DOS or WINDOWS support.

       Do certain applications hang or do all applications
       hang?  If it is specific to certain applications
       try changing some of the following settings:

              DPMI_MEMORY_LIMIT to 64
              DOS_RMSIZE to 624
              HW_ROM_TO_RAM to ON
              HW_TIMER  to ON (games or timing-sensitive
                                applications)
              IDLE_SECONDS to 60
              IDLE_SENSITIVITY to 100
              EMS_MEMORY_LIMIT (increase or decrease depending on
                                the applications needs)
              XMS_MEMORY_LIMIT (increase or decrease depending on
                                the applications needs)
              INT_DURING_IO to ON (Multimedia Applications and
                                   other DOS Applications)

      NOTE: These are general settings and may affect each
            application differently.  If the above information
            does not resolve the problem, contact OS/2 Support
            and ask for the DOS or WINDOWS application group

B.  If the entire system is hanging randomly, review the
    following:

    1. Run diagnostics to see if there is a hardware problem.
       The diagnostics diskette contains the hardware check
       program.

       -  MICRO CHANNEL SYSTEM (MCA) - For MCA Systems, get the
          diskette from the hardware vendor or Marketing
          Representative.
       -  INDUSTRY STANDARD ARCHITECTURE SYSTEM (ISA) - For ISA
          Systems, refer to the hardware manual that came with
          the system.

    2.  Add SET SHELLEXCEPTIONHANDLER=OFF to the second line
        of the CONFIG.SYS. This may produce an error message to
        the workplace shell when the system hangs.

    3.  Check IRQ's and comm ports.  The AT-BUS can not share
        IRQ's, Addressing, or DMA.  It can not skip comm port
        settings.

    4.  When OS/2 starts, it opens all applications that were
        previously running in OS/2.  If the workplace shell
        is displayed when the system starts and a previously
        opened application causes the system to hang do the
        following:

        A.  Add SET RESTARTOBJECTS=NO to the CONFIG.SYS.  When
            you start the sytem, the applications that were
            running under OS/2 when the system was shutdown
            will not restart.

            * If you have DOS on the system and OS/2 is
              using the Fat File System, use a DOS bootable
              or start DOS to edit the CONFIG.SYS and add the
              above statement.

            * If you do not have DOS on your system:
              1. Start the system with the Installation diskette.
              2. Insert diskette 1 when prompted.
              3. At the Welcome Screen, press Esc to go to the A:
                 prompt.
              4. Type X: and press Enter.  X: is the drive where
                 OS/2 resides.
              5. Type COPY CONFIG.SYS CONFIG.BAD to back up the
                 CONFIG.SYS. If a CONFIG.BAD already exists use a
                 different extention.
              6. Type ECHO SET RESTARTOBJECTS=NO >> CONFIG.SYS to
                 add the line to the CONFIG.SYS file.

        B.  You can also bring up the desktop without any
            applications opening by pressing Ctrl+Shift+F1 after
            the system loads the CONFIG.SYS.

            If you hear a beeping noise, remove your hands from
            the keys for a moment, then hold the keys down again.
            This procedure does not work as well as adding the
            SET RESTARTOBJECTS=NO statement to the CONFIG.SYS.



----------------------------------------------------------------
IBM disclaims all warranties, whether express or implied,
including without limitation, warranties of fitness and
merchantability with respect to the information in this document.
By furnishing this document, IBM grants no licenses to any
related patents or copyrights.