WIN-OS2 SESSIONS FAIL TO LAUNCH. BOOTLOG.TXT HAS AS IT,S LAST STATEMENT, "LOADSTART=MOUSE.DRV"

DESCRIPTION OF SYMPTOMS

    WIN-OS/2 fails to launch if there is no mouse type specified
    in MOUSE.INI

SUMMARY OF RESOLUTION

    Ensure the MOUSE.INI file has a type specified

DETAILS OF RESOLUTION

    When starting any WIN-OS/2 session (FS or Seamless), the session
    will terminate before it starts. If initiated from an ICON, it
    will hatch then unhatch. If initiated from a command line,
    "Loading Please Wait..." will appear, then the session prompt
    will re-display. If starting a WIN-OS/2 session from a command
    line with a "/B" switch, the BOOTLOG.TXT file will show
    LOADSTART=MOUSE.DRV as the last statement in the file. A look
    at MOUSE.INI reveals "MOUSETYPE=". That statement MUST equal the
    type of hardware installed on the system. When running in
    DOS/WINDOWS, the system will query the hardware attached and
    update MOUSE.INI accordingly. This is not occurring in OS/2.
    APAR PJ16247 has been created to address this problem. Until
    a resolution for the problem of why the MOUSE.INI file is not
    being updated as it is in DOS/WINDOWS, ensure the MOUSETYPE=
    statement in MOUSE.INI = <the mouse type described in the
    boot.description section in system.ini>.

Source