APAR Identifier ...... PJ16247
WARP IS NOT UPDATING MOUSE.INI WHEN LAUNCHING ANY WINOS2 SESSION
Symptom ...... AB WINAPAPAR Status ........... INTRAN
Severity ................... 3 Date Closed .........
Component .......... 562260100 Duplicate of .........
Reported Release ......... 300 Fixed Release ............
Component Name OS/2 WARP V3 Special Types ..
Current Target Date .. Type of Relief ..Not Available
SCP ................... OS/2 Platform ............ OS/2
Status Detail: Not Available
PE PTF List:
PTF List:
Parent APAR:
Child APAR list:
ERROR DESCRIPTION:
I. Problem Description: (General)
WIN-OS/2 is failing to launch if there is no mouse type
specified in MOUSE.INI
.
II Technical Description
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.
.
.
VII. APAR Screening Information:
.
1. Has the problem been recreated in Boca? YES
2. What configuration / settings changes were
tried? Edited MOUSE.INI to have the statement
= nothing. The statement is appearing in this form
among mamy users all with the same symptoms.
3. Does the problem occur in DOS / Windows? NO.
DOS/WINDOWS updates MOUSE.INI when Windows is
launched
.
.
.
VIII. APAR creation approved by: NG
.
LOCAL FIX:
If MouseType= is set to the type of mouse installed on the
system
If you need up to date information about the status of this problem, contact IBM and quote the APAR identifier.